In this track: From send to settlement
What is a replacement transaction?
A competing instruction can target the same sender nonce.
Two versions of numbered form 12 compete to fill the same processing slot. They are different forms, not an edit to a form already completed.
Nonce 4 is ready. Try submitting nonce 5 before including it.
A simplified local queue for ordinary account transactions. This model omits fee and other admission checks, and never signs or sends anything.
The nonce identifies the sequence position
A sender can authorize a new transaction with the same nonce as a pending one. It has its own encoded bytes and hash. The intention may be to increase fee settings or change the requested action.
Nodes apply their own pool policies
A node may require sufficient fee improvement before accepting a replacement into its local pool. Exact policies vary by client and configuration. There is no universal promise that any higher number will immediately replace every copy everywhere.
It remains a race until the history resolves
The original transaction might already be reaching a proposer. Different participants can know different candidates. In a single canonical account history, only one ordinary transaction can consume that sender nonce.
Replacement is not reversal
If a transaction has already been included, a replacement request does not erase it. A later reorganization is a different mechanism. Learn the canceling lesson to see why a wallet’s cancel label normally describes another competing transaction.
Does a replacement usually have the same transaction hash as the original?
The sender nonce can match while the encoded transaction and its fingerprint differ.
Original explanations by EtherTools. Examples are educational and source-linked; this site is independent of the Ethereum Foundation. Our approach.