What is Transaction Receipt?

1 min read Updated

A transaction receipt is the blockchain record generated after a transaction is processed — containing execution status, gas used, event logs, and other metadata that confirms how the transaction was executed.

WHY IT MATTERS

Transaction receipts are the detailed execution report. While the transaction itself specifies what was requested, the receipt documents what actually happened: success or failure, gas consumed, events emitted, and state changes.

Receipt fields include: status (1=success, 0=revert), gasUsed, logs (events emitted), blockNumber, transactionHash, and contractAddress (for contract creation). These are essential for verifying transaction outcomes.

For agent systems, receipt parsing is critical — the agent submits a transaction and must verify from the receipt that the intended action occurred as expected.

FREQUENTLY ASKED QUESTIONS

How do I get a transaction receipt?
Using eth_getTransactionReceipt with the transaction hash. Libraries like ethers.js provide wait() methods that return the receipt once the transaction is mined.
What does a 'reverted' status mean?
The transaction was included in a block but the EVM execution failed — a condition wasn't met, an assertion failed, or gas ran out during execution. State changes are rolled back but gas is consumed.
Can receipts be used as proof of payment?
Yes — the receipt provides cryptographic proof that a transaction was executed successfully, including the amount, recipient, and block timestamp.

FURTHER READING

Enforce policies on every tool call

Intercept is the open-source MCP proxy that enforces YAML policies on AI agent tool calls. No code changes needed.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.