Transaction and block context

Why use this example

Use this pattern when the answer depends on transaction fields, block data, chain identity, payable value, or live RPC state. The entry isolates transaction and block context so its input, result, and state changes stay easy to compare.

Solidity to run

msg.sender
tx.origin
address(this)
msg.value
msg.data
block.number
block.timestamp
block.chainid

What to expect

The transcript displays the configured caller and block fields alongside msg.data, msg.value, address(this), and tx.origin.

Continue the investigation

Change a value, add another expression, or open Inspect after the run. Accepted entries remain available to the next entry, and the clean replay keeps the complete result reproducible.