A stuck pending transaction is cleared by replacing it: rebroadcast at the same nonce with a higher fee, either as a speed-up (the identical transaction, better paid) or a cancel (a zero-value transfer to your own address, so the nonce is consumed by something harmless). A transaction gets stuck for one of two reasons: your max fee is below the network's current base fee, or an earlier transaction from the same account is blocking it at a lower nonce and freezing everything behind it. Neither move is guaranteed — a cancel costs gas, and the cheaper original can still land first — so watch a block explorer until one version confirms at that nonce and the other shows as dropped or replaced. Stuck-pending is largely an EVM phenomenon: on Solana a transaction simply expires if it is not processed within roughly a minute, and TON messages carry their own expiry, so there is nothing to cancel. Every replacement is a transaction you sign yourself, since WATS is fully non-custodial and never holds a key, and WATS charges its network fee in one token, ATS, instead of each chain's native gas token — that changes which token pays, not what the network charges, so leaving headroom in your max fee is still the real prevention.
The transaction that refuses to confirm
A transaction sits pending when no validator will include it in a block — usually because its max fee is below the network's current base fee, or because an earlier transaction from the same account is stuck ahead of it. The fix is a replacement: rebroadcast the same nonce with a higher fee, either as a speed-up (the same transaction, better paid) or a cancel (a zero-value transfer to yourself).
Nothing is lost while it waits — a pending transaction has cost you nothing yet, and your funds have not moved. But it is not harmless either: on nonce-ordered chains like Ethereum it silently blocks everything you try to send after it. Understanding why takes two minutes; fixing it takes one.
Why is my transaction stuck pending?
Two causes account for nearly every stuck transaction on an EVM chain.
Your max fee is below the current base fee. Under EIP-1559, every block sets a base fee that your transaction must at least match to be included. If demand spiked after you signed — or your wallet's estimate was tight and the market moved — your transaction waits in the mempool until the base fee falls back below your max, which can take minutes or simply never happen.
A nonce gap. Every EVM account numbers its transactions with a strictly sequential nonce — 0, 1, 2, and so on — and validators process them in order. If transaction 41 is stuck, transactions 42 and 43 cannot confirm no matter how generously you paid for them. This is why one cheap, forgotten transaction can freeze an entire wallet: everything behind it queues up, looking mysteriously broken. How the pricing side works end to end is covered in how gas fees actually work.
What does the speed-up button actually do?
Speed up is not a special network feature — it is a replacement transaction: the identical transaction, same nonce, same recipient, same amount, rebroadcast with a higher fee. Because a nonce can only ever be consumed once, validators keep whichever version pays more and drop the other. Most nodes require the replacement to raise both the max fee and the priority tip by a meaningful margin — commonly around 10% — or they ignore it as spam. Your wallet's speed-up button does exactly this: it pre-fills the original transaction, reuses its nonce, and bumps the fee for you.
How does cancelling a pending transaction work?
Cancel is the same replacement trick pointed at a different goal: your wallet sends a zero-value transfer to your own address at the same nonce, with a higher fee. If it wins, the nonce is consumed by a transaction that does nothing — and the original can never confirm. Two things surprise people. First, cancelling costs gas: the cancel is a real transaction that must be mined, so you pay the minimum transfer cost for it. Second, a cancel can lose the race — if a validator picks up your original before the cancel propagates, the original executes anyway and the cancel dies quietly.
Speed up or cancel — which one should I use?
| Speed up | Cancel | |
|---|---|---|
| What is sent | The same transaction, same nonce, higher fee | A zero-value transfer to yourself, same nonce, higher fee |
| Use when | You still want the action to happen | You regret it — wrong amount, wrong address, mistaken approval |
| Cost | Normal gas for the transaction, at the new rate | Minimum transfer gas, at the new rate |
| Can it fail? | Yes — the cheaper original can still land first | Yes — the original can win the race and execute anyway |
One rule applies to both: never treat a replacement as guaranteed. Until one version confirms on-chain, both exist, and the network — not you — decides which lands. If the original was dangerous, watch the explorer until you see which version confirmed at that nonce (the loser shows as dropped or replaced) before acting on the assumption it was stopped.
Does this happen on Solana or TON?
Stuck-pending is largely an EVM phenomenon, born from the combination of a persistent public mempool and strict per-account nonce ordering. Solana takes a different approach: every transaction references a recent blockhash and simply expires if it is not processed within a short window — roughly a minute — so there is nothing to cancel; you re-sign and resend. TON is different again: its messages carry their own expiry time, and there is no shared pending pool in the EVM sense, so the speed-up/cancel dance does not exist there either. If you came to EVM from either chain, this article is the missing manual. A multi-chain wallet like WATS spans both worlds — Ethereum, Arbitrum, Optimism, Base, Polygon and BNB Chain on the EVM side, Solana and TON on the other — so it is worth knowing which set of rules applies before you start hunting for a cancel button that was never going to exist.
How do I prevent stuck transactions?
- Leave headroom in your max fee. The max fee is a cap, not a bill — you only ever pay the base fee plus your tip, so a generous cap costs nothing extra and buys insurance against a sudden base-fee spike.
- Never spam retries at new nonces. Firing fresh attempts behind a stuck transaction just builds a queue that all waits on the same blocker — and multiplies the cleanup when you finally fix it.
- Fix the lowest nonce first. If several transactions are pending, only the oldest one matters; replace that one and the rest usually clear on their own.
- Keep the fee token topped up. A replacement is itself a transaction, so you need enough of whatever token pays fees on that chain to send it. Running out of a chain's native gas token is a common way to end up unable to fix your own stuck transaction; in WATS the fee token is ATS on every supported chain, so there is one balance to watch rather than eight.
- Glance at network conditions before signing. On a congested day, a fee estimate that looked fine an hour ago may already be below the going rate.
Where WATS fits
Nothing in this article is wallet-specific in the way people expect. A nonce belongs to your account on the chain, not to the app you sign with, so the replacement rules above hold from any wallet. What genuinely differs between wallets is what you must hold to pay for the fix. WATS charges network fees in a single token, ATS, instead of each chain's native gas token, using ERC-4337 account abstraction on EVM chains and LayerZero OFT to move omnichain across Ethereum, Arbitrum, Optimism, Base, Polygon, BNB Chain, Solana and TON. That is not a discount — the network charges what it charges, and a speed-up still has to outbid the original — but it does mean the one balance you keep topped up covers fees everywhere, instead of stranding you on the one chain whose gas token you happened to run dry. Collected ATS is burned, taking supply from 100M down to a 30M floor; the mechanics are on the ATS fee page. WATS is the first and only wallet to combine ERC-4337 and LayerZero OFT single-token fees, charged instead of native gas, with that burn.
The other WATS specific worth stating plainly is custody, because it decides who can act on a stuck transaction. WATS is fully non-custodial across all four products — the Chrome Extension, the mobile app, the Hot Wallet and the NFC Metal Card. You hold the keys and WATS never holds one. The direct consequence here is that nobody at WATS can reach into a pending transaction and edit it, and nobody can reverse one that has already confirmed. Every speed-up and every cancel is a new transaction that you sign, which is exactly why the checklist in this article is worth internalising rather than delegating.
Bottom line
A pending transaction is not lost money — it is an unpaid or blocked instruction sitting at a nonce, and the only lever you have is to replace it at that same nonce with a better-paid one. Speed up if you still want the action, cancel with a zero-value self-transfer if you do not, fix the lowest stuck nonce first, and confirm on an explorer which version actually landed before you assume anything. If the thing that keeps catching you out is gas — the wrong token on the wrong chain at the wrong moment — install WATS from the download page and keep one ATS balance for fees across all eight chains it supports, while holding your own keys throughout.
Frequently asked questions
How long can a transaction stay pending?
On Ethereum there is no protocol-level timeout — a pending transaction can wait indefinitely until it is included, replaced at the same nonce, or evicted from node mempools, which drop long-stale or underpriced transactions to free memory. Eviction is node policy, not a guarantee, and a dropped transaction can even be rebroadcast later. If you need certainty, replace it yourself with a speed-up or cancel rather than waiting for it to die.
Does cancelling a transaction cost gas?
Yes. A cancel is a real transaction — a zero-value transfer to your own address at the stuck nonce — and whichever version confirms pays its fee. You never pay for both, because a nonce can only be consumed once: if the cancel wins you pay its minimal transfer cost, and if the original wins you pay the original's fee. What no cancel can do is undo a transaction that has already confirmed.
Why are all my transactions suddenly stuck?
Almost certainly a nonce gap. EVM accounts process transactions in strict nonce order, so one underpriced transaction at the front blocks everything sent after it, no matter how well those later ones paid. Find the lowest pending nonce on a block explorer and replace that one with a higher-fee speed-up or cancel — once it confirms, the queue behind it usually clears on its own within a block or two.
Do I need ETH to speed up a stuck transaction in WATS?
WATS charges network fees in ATS instead of each chain's native gas token, so a replacement is paid for in ATS rather than in ETH on Ethereum or the native token of Polygon, BNB Chain, Solana or TON — on EVM chains that runs through ERC-4337 account abstraction. It changes which token pays, not what the network charges: a speed-up still has to outbid the original by a meaningful margin, and a cancel is still a real transaction with a real fee. The practical benefit is that one topped-up balance covers fees on every chain WATS supports, so you are less likely to be stranded because you ran out of the specific gas token you needed.
Can WATS cancel or reverse a transaction for me?
No, and neither can any genuine self-custody wallet. WATS is fully non-custodial — you hold the keys and WATS never holds one — so there is no WATS-side control that could reach into your pending transaction or claw back a confirmed one. A cancel is not a reversal: it is a competing zero-value transaction that you sign yourself at the same nonce, and it only works while the original is still pending. Once a transaction confirms on-chain it is final, whichever wallet you signed it from.