Encyclopedia Ethereum · Entry 105
Speeding up or cancelling an Ethereum transaction
In this article
At a glance
Key facts
| Fact | Detail | Source |
|---|---|---|
| Competition | The replacement and original compete for one sender nonce. | [1][4] |
| Hash | Changing the signed transaction creates a different transaction identifier. | [2] |
| Limits | A same-nonce attempt cannot reverse a nonce already consumed in the accepted chain. | [2] |
Speeding up usually preserves the intended action
A wallet can build a higher-fee attempt using the same recipient, value and call data. Both fee caps may matter under EIP-1559-style pricing, and exact admission thresholds depend on node software and configuration.
Inspect the final recipient, value, calldata and maximum fee. A familiar wallet label does not substitute for reviewing the transaction actually being signed.
Cancellation is a race, not a command to validators
A wallet may attempt to occupy the nonce with a different operation instead of the original request. If that alternative is included first, the original cannot also consume the same sender nonce.
If the original is included first, the competing cancellation loses. For this reason, an interface must not describe submission of a cancel attempt as proof of cancellation.
After inclusion, inspect the winning receipt
Follow the hash of the transaction that actually entered the block. A replaced attempt can remain visible in a wallet history or external service without becoming the executed payment.
Once a transfer has executed, moving assets back generally requires a new authorized operation. Replacement is not a refund mechanism.
Direct answers
Questions people ask
Does a higher fee guarantee my replacement wins?
No. Nodes must accept the replacement, it must reach block builders in time, and the original must not already have been included.
Inspect the evidence
The answer and key facts have stable claim links. These records retain the scope and qualification when reused.
An Ethereum replacement uses the same sender and transaction nonce as a pending transaction while changing fields such as fees. Nodes apply their own transaction-pool replacement rules. The first valid competing transaction included consumes that nonce; a replacement cannot undo an already executed transaction.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T18:12:41.505Z.
Link to this claimCompetition: The replacement and original compete for one sender nonce.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T18:12:41.505Z.
Link to this claimHash: Changing the signed transaction creates a different transaction identifier.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T18:12:41.505Z.
Link to this claimLimits: A same-nonce attempt cannot reverse a nonce already consumed in the accepted chain.
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 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 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 - Geth command-line optionsGo Ethereum
Implementation-configurable transaction replacement and local pool policies.
Locator: txpool.pricebump; txpool.lifetime · Retrieved: 2026-10-02T17:25:58.872ZOpen 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 - Fee market change for ETH 1.0 chainEthereum Improvement Proposals
Base fees, fee caps, priority fees and effective transaction gas price.
Locator: Specification · Version / scope: EIP/ERC-1559; retrieved document hash recorded · Retrieved: 2026-10-02T17:03:42.151ZOpen source - Geth legacy-pool replacement checksGo Ethereum
Versioned same-nonce replacement policy and EIP-1559 fee-cap conditions.
Locator: list.Add; gasFeeCap and gasTipCap replacement thresholds · Version / scope: go-ethereum v1.15.11 · Retrieved: 2026-10-02T17:55:17.128ZOpen 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
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. “Speeding up or cancelling an Ethereum transaction.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/ethereum-transaction-replacement/