Receipt: Evidence of Included Execution, with Specific Limits
A transaction receipt describes an observed execution included in a block. It is different from the transaction request itself, an explorer’s pending label or a provider’s quote identifier.
Begin with the identity and observation
Use the public transaction hash on the intended chain, then compare the receipt’s transaction and block fields. Ethereum’s JSON-RPC documentation describes receipt queries and their results. A null or missing receipt does not mean a successful zero-value transaction; the request may be pending, unknown to that node or queried on the wrong chain. Record the source and time when evidence is unavailable.
Read status as execution evidence
A receipt status can distinguish successful execution from a revert for the included transaction. Success does not establish that the user’s broader goal was correct. A successful approval may change permission without moving swap output; a successful transfer may use the wrong recipient. Compare the operation and resulting evidence rather than converting a single status flag into an unconditional statement that everything intended happened.
Use logs and gas fields for different questions
Logs can help identify token events emitted by the executing contracts. Gas fields help explain execution cost in combination with the applicable fee rules. They do not all measure the same quantity: cumulative gas within a block differs from this transaction’s gas use. Layer-two networks may expose additional fee information. Decode logs using the actual contract and avoid treating an untrusted event name as independent proof of asset legitimacy.
Keep inclusion and finality separate
The block in a receipt identifies where execution was observed, while stronger confirmation or finality depends on the network. Recheck relevant evidence if the chain reorganizes or your use case requires finalized state. RunixCoin’s public quote does not submit a swap and therefore is not a receipt. This glossary page sends no requests and makes no claim that a real-money RunixCoin transaction was tested.
References and verification
Reviewed . Product limits reflect inspected public interface code. These are educational checklists, not reports of tested mainnet transactions; browser behavior and execution were not verified.