Encyclopedia Ethereum · Entry 04
Ethereum transactions and nonces: how requests stay in order
In this article
At a glance
Key facts
The destination and the recipient may describe different things
A simple ETH payment names the recipient in its destination field. A token transfer instead calls a token contract; the intended token recipient is an argument inside the call data. The top-level ETH value may be zero.
That is why a wallet or explorer needs to decode more than the amount field. A zero-ETH transaction can move valuable tokens, create an allowance or change a contract’s settings.
Follow the earliest unfinished sender nonce
If the next ordinary sender nonce is 12, a transaction using nonce 13 cannot simply execute first in that account’s sequence. It may wait while nonce 12 is missing or pending. A wallet can group these as several pending actions even though the earliest gap explains the queue.
A same-nonce replacement competes for the original slot; a new-nonce transaction is another operation. Once an included transaction uses the nonce, even a top-level execution failure does not make that nonce available for an unrelated retry.
A receipt separates failure from a request still waiting
Before inclusion, a receipt may be unavailable. After inclusion, its status distinguishes successful execution from failure. A reverted operation can still consume gas because nodes performed work before the failure occurred.
For example, a transfer attempt might fail because a contract’s balance check rejects it. The requested transfer does not take effect, but a recorded transaction and fee can remain. Read status and logs alongside the headline amount.
Nonce order is not the same as settlement finality
The nonce describes account-level replay and ordering rules; finality describes the chain’s agreement about its history. A receipt in a recent block and a finalized transaction answer different questions.
Account delegation and contract-created operations add detail beyond the simplest nonce counter story. In particular, EIP-7702 authorization can also affect an account nonce. Use the relevant wallet and protocol rules rather than treating a nonce as merely a lifetime payment count.
Direct answers
Questions people ask
Does a transaction hash mean the payment worked?
No. It identifies a transaction; check whether it was included, its execution status and the applicable confirmation or finality state.
Can a failed transaction have a network fee?
Yes. Work performed during an included transaction can be charged even when execution fails or a contract reverts.
Can I cancel an already finalized payment?
Submitting another transaction cannot erase a finalized payment. Pending replacement is a race before execution, not an onchain undo function.
Inspect the evidence
The answer and key facts have stable claim links. These records retain the scope and qualification when reused.
An Ethereum transaction is a signed request to change network state. Its fields identify the destination, any ETH value, call data and fee limits. A sender nonce orders ordinary transactions and prevents the same authorized transaction from executing repeatedly; a transaction hash alone does not prove inclusion or success.
Scope: Ethereum. Verification: verified · 2026-10-02T18:16:35.976Z.
Link to this claimValue: The native ETH amount, denominated in wei
Scope: Ethereum. Verification: verified · 2026-10-02T18:16:35.976Z.
Link to this claimData: May encode a contract function and arguments
Scope: Ethereum. Verification: verified · 2026-10-02T18:16:35.976Z.
Link to this claimReceipt: Reports execution status after inclusion
Scope: Ethereum. Verification: verified · 2026-10-02T18:16:35.976Z.
Link to this claimRevision history
- — First publication after primary-source research and independent automated verification.
- — Expanded explanation: Follow the earliest unfinished sender nonce. Worked examples are illustrative; source checks and independent verification are recorded separately.
On the Understand Ethereum path · Learn next: Ethereum gas fees: units, prices and the amount actually paid
Source register
Sources and references
Retrieval dates and locators are recorded individually.- Ethereum transactionsethereum.org contributors
Supports nonce ordering, value versus calldata, signed transaction fields, receipts and transaction inclusion.
Locator: What is a transaction; the data field; transaction lifecycle · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:40.399251+00:00Open source - Ethereum accountsethereum.org contributors
Supports accounts versus wallet software and account state fields. The older empty-code EOA description is qualified using EIP-7702.
Locator: Account types; an account examined; a note on wallets · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:40.369782+00:00Open source - JSON-RPC APIethereum.org contributors
Defines chain identity, balance/nonces, read-only simulation and receipt/status/log fields.
Locator: eth_chainId; eth_getBalance; eth_getTransactionCount; eth_call; eth_getTransactionReceipt · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:47.605538+00:00Open source - Interacting with smart contractsethereum.org contributors
Supports read-only calls, state-changing transactions, ABI decoding and limits of simulation.
Locator: Reading; writing; understanding contract ABIs; events and logs; simulating · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:40.398262+00:00Open source - Gas and feesethereum.org contributors
Supports gas units, ETH/gwei units, base/priority fees, resource limits and charges for executed failed transactions.
Locator: How are gas fees calculated; base fee; gas limit · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:40.393022+00:00Open source - Proof of stakeethereum.org contributors
Supports 12-second slots, 32-slot epochs, stake-weighted checkpoint voting and block verification.
Locator: Validators; transaction execution; finality; fork choice · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:43.818781+00:00Open source - EIP-7702: Set Code for EOAsEthereum Improvement Proposals
Defines persistent EOA code delegation, continued transaction origination and the account-wide consequences of delegate code.
Locator: Abstract; persistence of code delegation; transaction origination; security considerations · Version / scope: ac912ca6a9685590345dd8e5736cda75976d0131 · Retrieved: 2026-10-02T14:35:51.249142+00:00Open source - 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 - 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
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 transactions and nonces: how requests stay in order.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/ethereum-transactions-and-nonces/