How Nonce Conflicts Stall Wallet Swaps
A pending lower nonce can hold up wallet swaps. Learn how nonce ordering, transaction replacement and wallet checks can clear the queue safely.
BitCurrent Newsroom2 min read
A wallet swap can stall when its next account nonce is already tied to a pending transaction. On EVM chains, wallets assign each outgoing transaction a sequential nonce, or account counter.
How does a nonce conflict block a swap?
Transactions from one account must be processed in nonce order. If a transaction with nonce 12 is still pending, a swap sent with nonce 13 usually cannot execute first, even if it has a higher fee.
The blockage can start with a transaction that was broadcast but not confirmed, perhaps because its fee no longer attracts validators. A wallet may then build a new transaction using the same next nonce. Nodes generally treat that as a replacement attempt, and their acceptance rules can differ.
For the separate mechanics of moving funds between chains, see how QuickSwap cross-chain swaps settle. That settlement has its own confirmation stages; it does not clear a pending nonce on the source wallet.
What can a wallet user do when a swap is stuck?
First, check the transaction status and nonce in the wallet or a block explorer for the relevant chain. Confirm which transaction is pending before submitting another one. A second swap may simply join the queue behind it.
- Wait if the pending transaction still has a reasonable chance of confirmation.
- Speed up by resubmitting that transaction with the same nonce and a higher fee, if the wallet offers that option.
- Cancel by sending a replacement transaction with the same nonce, if supported. Cancellation is not certain until the replacement is confirmed.
When does replacing a transaction help?
A replacement can free later transactions only if it is accepted and confirmed at the blocking nonce. Fee requirements vary by network and node, so a small fee increase may not replace the original. If the original confirms first, the replacement may fail as stale.
Check that the wallet is set to the intended network and account, then compare its pending transaction with the chain’s record. Avoid repeatedly sending swaps: that can create more queued transactions without resolving the first one. The key is to address the oldest pending nonce, then let later transactions proceed in order.