Nonce too low during a swap: check what already confirmed

A nonce-too-low error usually means the submitted transaction uses an account nonce below the next valid one. Another transaction may already have consumed it, including a swap or cancellation you thought was still pending.

Ethers documents this error as a nonce lower than the next required nonce. This is about transaction ordering, not slippage or token price.

Find what used that nonce

Inspect outgoing account activity on the correct chain. Compare the nonce and full hash of the attempted swap with confirmed transactions and any wallet replacement history.

If a prior swap succeeded, do not initiate a new trade unless you intend a second exchange. If a cancellation confirmed, its consumption of the nonce is expected. If the earlier transaction failed onchain, the failed inclusion still belongs in the account’s sequence.

Resolve stale local information

Refresh the wallet and application after checking the chain. If you use the same account across several wallet applications, one can submit activity the other has not reflected yet.

A manually chosen higher nonce is not a universal solution; it can create gaps that block later transactions. Let the wallet reconcile current state or consult official support when it cannot.

When no matching account activity is visible, consider whether you searched the wrong network or whether the provider is stale. Preserve the error and attempted nonce. Clearing local history without understanding the confirmed sequence can hide useful evidence while leaving the underlying issue unchanged.