Jump to content
Crypto Front Page

Crypto networks, markets and policy

Why Gas or an Earlier Nonce Delays an Ethereum Approval

Why is my token approval pending on Ethereum? Check its fee, transaction hash and oldest pending nonce to find what is holding up a ShibaSwap trade.

The Crypto Front Page Desk4 min read

Why Gas or an Earlier Nonce Delays an Ethereum Approval

A token approval on Ethereum stays pending when its gas fee is too low for current demand or an earlier transaction from the same wallet is still waiting. Check the approval’s transaction hash, then look for an older pending transaction from your address; Ethereum confirmation shows when the wait is over.

For a shiba swap trade, the approval is a separate transaction that lets a spender use a set amount of your ERC-20 token. The swap can use that allowance after the approval confirms. For more on how long a ShibaSwap trade can stay stuck, see our article on that question; this post focuses on why an approval waits.

An approval waits for gas or an earlier nonce

An Ethereum approval waits in the account’s transaction queue until Ethereum includes it in a block. Each transaction from an account has a nonce, a number that sets its place in that account’s sequence. Ethereum processes those transactions in nonce order, so a later one cannot pass an earlier pending one.

Gas is the fee paid to process a transaction. When Ethereum is busy, the priority fee offered with a transaction may be too low for validators to include it soon. The approval can then remain pending even if the wallet shows that it was submitted successfully. That status means the wallet sent the transaction; it does not mean Ethereum confirmed it.

Take an illustrative case: you submit an ERC-20 approval in MetaMask, then see it marked “pending.” The approval has a nonce, but a transfer you submitted earlier from the same address through another app may have the previous nonce. The approval must wait for that earlier transaction to confirm or be replaced. Transactions from other wallets do not hold up your account’s nonce sequence.

Start with the approval’s transaction hash in MetaMask and open it on an Ethereum block explorer. Compare the explorer’s status with the wallet’s label: they can use different wording, so confirmation on Ethereum is the key status. Then inspect transactions from your address and find the oldest one still pending. If it has a lower nonce than the approval, that earlier transaction is holding up the queue. If the approval is the oldest pending transaction, its own fee may be the issue.

A speed-up typically replaces a pending transaction with another using the same nonce and a higher fee. Before confirming, read the replacement details in your wallet and make sure they match the transaction you intend to speed up. If it is the earlier transaction that is stuck, speeding up the later approval alone will not let it pass. After the replacement confirms, the queue can move forward in nonce order.

Before the earlier transaction confirms, the approval may still show as pending and the swap may remain unable to use its allowance. After confirmation, that earlier transaction is no longer blocking the next nonce; the approval itself still needs Ethereum confirmation before the allowance is available. The thing that changed is the queue position that was blocking progress. The token, wallet address and requested approval remain the same.

Related

How to speed up a pending Ethereum transaction

To speed up a pending Ethereum transaction, use your wallet’s replacement or speed-up option and review the higher fee and same nonce before confirming. This can help when that transaction is the oldest one waiting in your account’s queue.

How to check an Ethereum transaction on a block explorer

To check an Ethereum transaction on a block explorer, search its transaction hash and read the status and nonce. Then check your address for an earlier pending nonce. Revisit the diagnosis if Ethereum confirms the approval but the swap still cannot proceed: at that point, the account’s pending transaction queue is no longer the cause to check.