WORLDCRYPTOCURRENCY GUIDE
Practical analysis

Pending transactions: nonce, replacement and fees

Distinguish unbroadcast, pending, replaced and confirmed operations, and understand speed-up and cancellation limits.

A person looking at a computer at a work table
Educational illustration — A person looking at a computer at a work table
Short answer

A pending transaction is not necessarily lost. Check network, hash and status before replacement; this mechanism cannot cancel a confirmed transaction.

Establish observable status

Wallet and explorer

Understand Ethereum nonces

Account ordering

Interpret cancellation

A transaction race

01

Establish observable status

Start with transaction hash and correct network. Pre-broadcast failure, node rejection, mempool entry and confirmation are different states. An explorer may not have seen a broadcast; absence alone does not prove nothing was sent. Compare wallet status and public data without sharing recovery secrets.

02

Understand Ethereum nonces

Ordinary Ethereum account transactions execute in nonce order. Later transactions may wait for the previous nonce. Replacement proposes another transaction with the same nonce and fee conditions acceptable to relevant nodes. Requirements vary by client and network; randomly increasing a field does not guarantee acceptance.

03

Interpret cancellation

A wallet cancellation often submits another transaction with the same nonce, sometimes to yourself. The original can be included first. You may pay fees even though the commercial goal was not met. Once confirmed, replacement does not erase history: assess the result and any separate follow-up action.

04

Replace a Bitcoin transaction

Bitcoin replacement submits a competing transaction spending shared inputs. Relay policy, fees and wallet capability govern acceptance; historic signalling rules do not describe every current policy. Verify controlled outputs and the intended recipients in the replacement. Never give wallet keys to an unknown acceleration service.

05

Calculate parent-child fees

Hypothetical parent: 200 vB and 200 satoshis. Child: 100 vB and 1,300 satoshis. Together they pay 1,500 for 300 vB, or 5 sat/vB. The child must spend a controlled parent output. This is an average rate, not an inclusion guarantee: package policy, competition and miner choices still matter. It cannot accelerate arbitrary incoming payments.

06

Prevent duplicate actions

Record original and replacement hashes, amounts, fees and final status. Do not create another independent purchase or transfer until you understand the first. Temporary balance changes may include pending activity. Ask a merchant which payment was recognised; for token approvals, also check actual execution.

Compare

Scenarios and model limits

SituationInterpretation
Ethereum: earlier nonce pendingMay hold up later account transactions.
Hypothetical CPFP: 1,500 sat / 300 vBPackage rate 5 sat/vB, without guaranteed inclusion.
Confirmed transactionReplacement does not remove confirmation.
FAQ

Frequently asked questions

Can I replace a confirmed transaction?

Replacement targets pending operations. It does not remove an already confirmed transaction.

Why is the next transaction waiting?

An unexecuted earlier Ethereum nonce can hold up later ordinary account transactions.

Do higher fees guarantee confirmation?

No. They may improve competitiveness under applicable rules without promising a block or deadline.

Verifiable sources

Independent educational content reviewed against primary documentation. No personalized recommendation or promise of returns. Updated October 3, 2026

Related terms

CPFP
Child transaction spending a controlled parent output to raise the combined average fee rate.
RBF
Replacement of a pending Bitcoin transaction by a competing transaction under applicable policies.