Start your 3-day free trial
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.


If a crypto transaction is stuck, its offered fee may no longer be competitive, but “pending” does not prove that diagnosis. First confirm that the transaction was broadcast on the intended network, remains pending in its mempool, and is the oldest unresolved nonce; then decide whether to wait, speed it up, or attempt cancellation.
Key Takeaways
- A wallet label is not enough; inspect the transaction hash on the correct network.
- Low fees, nonce gaps, dropped transactions, RPC lag, and failed execution require different actions.
- Speed-up and cancellation normally compete with the original using the same nonce.
- A confirmed transaction cannot be canceled, and a replacement attempt is not guaranteed to win.
Use the online security guide to reach your wallet and explorer independently. Anyone asking for your seed phrase or private key to “clear the mempool” is trying to take control of the account, not repair a public transaction.
Check the transaction hash in an explorer for the exact network. A genuine pending result means the network knows about the transaction but has not included it in a block. A hash that is unknown may indicate delayed broadcast, RPC disagreement, a dropped transaction, or the wrong explorer.
Ethereum separates the gas used by execution from the price paid per unit of gas. Under its current fee model, the sender sets a maximum fee and a priority fee, while the protocol determines a base fee for each block.[1] A transaction can wait when its effective offer is below what current blocks accept, but fee competition is only one branch.
| Observation | Likely branch | Safe next check |
|---|---|---|
| Pending in the correct explorer | Mempool and fee competition | Nonce, offered fee, current wallet estimate |
| Not found anywhere on that network | Broadcast or dropped state | Wallet RPC, another reputable explorer, sender log |
| Confirmed successfully | No longer cancellable | Recipient and application state |
| Confirmed with failure | Execution reverted | Error, gas used, contract call; do not replay blindly |
| Later nonce also pending | Earlier nonce may block the queue | Find the oldest unresolved nonce |
| Exchange says pending, no public hash | Custodian has not broadcast | Platform status and official support |
The last row belongs to the pending exchange withdrawal guide, not to a self-custody gas replacement procedure.
Copy the full transaction hash and record the network, sender, destination, value, token contract if applicable, nonce, submitted time, gas limit, maximum fee, priority fee, and current explorer status. Keep the wallet's original intent visible: the destination and call data matter as much as the fee.
Check the sender address's transaction list. Account-based EVM networks process transactions from one address in nonce order. If nonce 41 is unresolved, a transaction with nonce 42 may wait even when its own fee is attractive.
Do not reset wallet data, clear activity, or submit several replacements before preserving this evidence. A local reset may hide the wallet entry without changing the public mempool, and multiple same-nonce candidates make the result harder to follow.
Waiting is reasonable when the transaction remains valid, is not urgent, and its fee is near the range currently being included. Network demand can fall, allowing the original offer to be mined without another action.
The decision depends on the network and transaction. Check a reputable fee estimator for the same chain, but do not treat an estimate as a promise. Validators and builders choose transactions under current conditions, and different mempools may see different candidates.
If the transaction disappears from explorers, do not assume that it was confirmed. Verify the sender's current nonce and balance. A dropped transaction may be resubmitted by the wallet, or the nonce may become available again, but the correct action depends on what the network now recognizes.
Use the wallet's built-in speed-up function when it supports the network and transaction type. Review the replacement in full: it should preserve the intended recipient, value, call data, and nonce while offering a fee the network is more likely to accept.
MetaMask describes speed-up as resubmitting the same transaction with the same nonce and a higher fee.[2] The original and replacement then compete; only one transaction for that sender and nonce can become canonical.
Before signing:
Do not copy a fee or nonce supplied by a stranger. Do not call an unknown contract method to “unstick” the transaction. The wallet's own replacement flow is safer than an improvised transaction because it preserves the original fields for review.
Cancellation is an attempt to replace the original before it is confirmed. A wallet may create a zero-value transaction from your address to itself using the same nonce and a competitive fee. If that replacement is included first, the original cannot later use that nonce on the canonical chain.
MetaMask explicitly notes that cancellation can only be attempted while the transaction remains pending.[2] It is not a recall request sent to a central operator. The original can win the race while you are preparing or broadcasting the cancellation.
Review the cancel transaction as carefully as any transfer. Confirm the sender, recipient, nonce, network, value, and fee. If a wallet asks you to disable a feature or expose advanced controls, follow only its current official instructions and restore normal settings afterward.
Start with the lowest unresolved nonce. Replacing a later transaction does not make the account skip an earlier valid nonce. Once the earliest nonce is confirmed or successfully replaced, later transactions may begin moving.
List every pending candidate by nonce and hash. Same-nonce entries are alternatives; consecutive nonces are a queue. This distinction prevents paying to replace the wrong item.
If the wallet shows more transactions than the explorer, refresh the network view and compare the account's current confirmed nonce. Do not assume every local activity entry is still propagated across the network.
Inclusion is only one stage. A bridge may require source-chain confirmation, message delivery, a challenge period, and destination execution. Replacing the source transaction is appropriate only while that exact transaction is pending.
After source confirmation, use the bridge transfer state checklist. Do not send another deposit or manually call a bridge contract until you know which stage owns the delay.
Similarly, a confirmed token approval or swap can lead to a later application action. Verify each hash and contract event separately. “The app still spins” does not make a confirmed transaction pending again.
There is no universal duration. It depends on network rules, demand, the offered fee, node mempool policies, and whether the transaction remains propagated. Use the current chain evidence instead of a generic timer.
Only the transaction that is included consumes execution gas on the canonical chain, but wallet behavior and network-specific mechanics can vary. Review the replacement cost and final receipt rather than assuming a quoted total.
Not to replace the original. A replacement normally uses the same sender and nonce. A higher nonce may remain queued behind the unresolved earlier one.
The wallet may have stale local activity, use a lagging RPC endpoint, or have failed to broadcast widely. Check another reputable explorer for the same network and compare the account's current nonce.
No. Once the original is confirmed in the canonical chain, a same-nonce cancellation cannot undo it. Any recovery must address the resulting asset or application state.
No. A failed transaction was included but its execution reverted; its nonce was consumed and gas was used. Diagnose the error before considering a new transaction.
Preserve the hashes and transaction fields first. Clearing local activity does not remove a transaction from the network and can make the investigation harder.
No. Confirmations usually count blocks built after inclusion, while finality is defined by the network's consensus rules. The confirmations and finality explainer separates those guarantees.
Disclaimer: This article provides general technical information, not financial or recovery advice. Replacement behavior, fee rules, and wallet controls vary by network and software version.
Sources:
Sources checked 9 September 2026.
Related articles:
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.





