In this track: From send to settlement
What is a transaction receipt?
A result record for a transaction included in a block.
A shop receipt records the outcome and resource details of a processed request. It is different from the order form you originally submitted.
Maya prepares an instruction: send 0.01 pretend ETH to Leo.
A local simulation. Nothing is signed or sent to a network.
Read the execution outcome
A modern Ethereum transaction receipt includes a status describing whether top-level execution succeeded or failed. A null receipt response can mean a transaction has not been included in that provider’s view; it is not automatically proof of permanent disappearance.
Read the resource fields
Gas used describes consumed execution resources. Effective gas price helps calculate the execution fee. Cumulative gas used is a different field: it totals gas up to that transaction’s position in the block.
Logs tell part of the story
The receipt includes surviving logs emitted during successful execution paths. For contract creation, it can identify the created contract address. Token-transfer displays in an explorer often interpret particular logs and interfaces.
Keep the block context
A receipt is associated with a block hash and position. If an unfinalized chain reorganizes, the accepted receipt context can change. The record’s presence does not alone establish economic safety or finality.
Is cumulative gas used the same as this transaction’s individual gas used?
Cumulative gas includes earlier transactions in the block as well.
Original explanations by EtherTools. Examples are educational and source-linked; this site is independent of the Ethereum Foundation. Our approach.