Insights on Crypto Payments, Infrastructure, and Operations

Blockchain Receipt

Pronunciation: BLOCK-chain ree-SEET

Also known as: On-Chain Transaction Receipt, Execution Receipt

Definition

A blockchain receipt is a protocol-defined record produced after a transaction is processed, commonly containing execution status, gas usage, logs, and references to the transaction and block. It is evidence of how the network handled the transaction, not a merchant receipt or proof of legal payment. Receipt contents differ by blockchain, so applications must use chain-specific fields and confirmation rules.

Overview

Blockchain Receipt describes the execution record associated with a transaction after a node applies it to the chain state. On Ethereum, transaction receipts expose status, cumulative or per-transaction gas information, contract creation details, and emitted logs. The receipt is committed through the block’s receipt structure and can be queried through node APIs.

A receipt answers questions that the signed transaction alone cannot. The transaction shows the sender’s requested action, while the receipt shows whether top-level execution succeeded and which Event Log records were produced. A transaction can be included in a block yet fail during execution, consuming gas without applying the intended state changes.

The term should be distinguished from a general Receipt issued by a wallet, merchant, or payment application. A blockchain receipt is a protocol data object. It does not identify the purchaser, describe goods, establish tax treatment, or prove that an off-chain order was fulfilled.

Payment and integration systems use receipts to confirm contract calls, token transfers, and deployment results. They should query the receipt from a trusted node or provider, verify that it belongs to the expected transaction and chain, and wait for the required confirmation level. Logs should be decoded against the correct contract interface.

Receipt schemas and semantics vary across protocols and upgrades. Fields can be added, replaced, or exposed differently through APIs. Reliable software preserves the raw receipt, uses version-aware decoders, and cross-checks critical results with State Verification or the expected state change rather than relying on one display field.

Receipt availability can lag behind initial transaction visibility, particularly when different providers serve pending and confirmed data through separate pipelines. Integrations should retry a missing receipt after inclusion rather than interpreting absence as failure, while still enforcing timeouts and provider-health checks.

Key Takeaway

A blockchain receipt records the network’s execution result for a transaction, but it is not a commercial receipt and must be interpreted with chain-specific rules.

Sources

  1. EIP-658: Embedding Transaction Status Code in Receipts — Ethereum Improvement Proposals (2026-08-02)
  2. Ethereum.org Documentation: Transactions — Ethereum.org (2026-08-02)
  3. Ethereum.org Documentation: Data and Analytics — Ethereum.org (2026-08-02)