Encyclopedia Ethereum · Entry 101
Ethereum transaction hashes: an identifier, not proof of success
In this article
At a glance
Key facts
| Fact | Detail | Source |
|---|---|---|
| Identifier | The RPC transaction object exposes a hash field. | [2] |
| Pending | Block fields can be null while a transaction is pending. | [2] |
| Result | Execution outcome belongs in the receipt’s status, not in the identifier itself. | [3][2] |
One identifier, several possible states
A wallet signs a transaction before submitting it to a node. A node may know it while it waits for inclusion. Once included, a receipt records its execution outcome and the block containing it.
A link labeled “transaction sent” is therefore a starting point for inspection. It is not interchangeable with successful execution or finality.
A replacement is a different transaction
Two transactions can compete for the same sender nonce. Changing signed transaction fields produces a different encoded transaction and identifier. Only the transaction actually included consumes that nonce in the accepted sequence.
A wallet’s activity list may group several attempts as one payment. Follow the identifier attached to the final included attempt rather than assume the first hash must succeed.
Always pair the hash with a chain
A lookup service operates against a particular chain. An absent result on Ethereum mainnet says nothing conclusive about whether the transaction was submitted to a rollup or test network.
Record the chain, hash and observed block together when citing a transaction. For a smart-account user operation, distinguish the operation identifier from the bundler’s enclosing transaction hash.
Direct answers
Questions people ask
Does a transaction hash mean the recipient has received the tokens?
No. The transaction may still be pending or may fail, and successful top-level execution alone does not establish every intended token transfer. Inspect the actual receipt and token outcome.
Inspect the evidence
The answer and key facts have stable claim links. These records retain the scope and qualification when reused.
An Ethereum transaction hash identifies the encoded transaction, not its outcome. It can be known before inclusion and does not prove execution succeeded. Look it up on the correct network, then inspect the receipt, block position and relevant balance or event changes.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T18:12:41.505Z.
Link to this claimIdentifier: The RPC transaction object exposes a hash field.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T18:12:41.505Z.
Link to this claimPending: Block fields can be null while a transaction is pending.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T18:12:41.505Z.
Link to this claimResult: Execution outcome belongs in the receipt’s status, not in the identifier itself.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T18:12:41.505Z.
Link to this claimRevision history
- — First publication after primary-source research and independent automated verification.
Source register
Sources and references
Retrieval dates and locators are recorded individually.- Ethereum transactionsethereum.org contributors
Signed transaction fields, nonces, propagation, inclusion and transaction types.
Locator: The transaction lifecycle; Typed transaction envelope · Retrieved: 2026-10-02T17:03:41.854ZOpen source - Ethereum JSON-RPCethereum.org contributors
RPC response fields, transaction receipts, call simulation and log filtering.
Locator: eth_getTransactionByHash; eth_getTransactionReceipt; eth_call; eth_getLogs; eth_getCode; eth_estimateGas; eth_getBalance; eth_getStorageAt; eth_getTransactionCount; default block parameter · Retrieved: 2026-10-02T17:03:42.060ZOpen source - Embedding transaction status code in receiptsEthereum Improvement Proposals
Receipts report top-level execution success or failure.
Locator: Specification · Version / scope: EIP/ERC-658; retrieved document hash recorded · Retrieved: 2026-10-02T17:03:42.150ZOpen source - Ethereum accountsethereum.org contributors
Key-controlled and code-controlled accounts, balances, nonces and storage.
Locator: Account types; An account examined; Account creation · Retrieved: 2026-10-02T17:03:41.958ZOpen source - Simple replay attack protectionEthereum Improvement Proposals
Transaction chain ID domain separation; not blanket protection for all signatures.
Locator: Specification · Version / scope: EIP/ERC-155; retrieved document hash recorded · Retrieved: 2026-10-02T17:03:42.312ZOpen source - Account Abstraction Using Alt MempoolEthereum Improvement Proposals
User operations, bundler transaction submission and paymaster validation.
Locator: Specification; Bundlers; Paymasters; Security Considerations · Version / scope: EIP/ERC-4337; retrieved document hash recorded · Retrieved: 2026-10-02T17:03:42.486ZOpen source - ERC-20 Token StandardEthereum Improvement Proposals
Token supply, displayed units and balance accounting.
Locator: totalSupply; balanceOf; transfer; decimals; approve; allowance; transferFrom; Transfer · Version / scope: ERC-20 · Retrieved: 2026-10-02T17:03:45.826ZOpen source
Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.
Editorial method and correctionsDegrees of Satoshi editorial project. “Ethereum transaction hashes: an identifier, not proof of success.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/ethereum-transaction-hashes/