Swap failed but gas was charged: what happened?
Find out why a reverted swap still costs gas, how to verify the receipt, what happens to your input tokens and what to check before retrying.
Explore the reference
Identify failed, pending or unexpected transactions using the evidence recorded on-chain.
50 guides · Page 1 of 3
Find out why a reverted swap still costs gas, how to verify the receipt, what happens to your input tokens and what to check before retrying.
Recognize token-level pause or address restrictions that a wallet setting cannot override.
Compare the current spender allowance with the actual amount required after an approval appears to have succeeded.
Understand what a pending approval means for your next swap and how to avoid stale quotes or duplicate permission transactions.
Understand the limits and cost of attempting to replace a pending swap with a cancellation transaction.
A successful outer transaction does not always prove every intended swap step ran; verify settlement and recipient balances.
Follow the confirmed replacement hash to determine whether an earlier pending swap executed, changed or was cancelled.
A dropped transaction can reappear, so verify account nonce and submission state before retrying a swap.
Why an account with enough input tokens can still be unable to pay for approval or swap execution.
Resolve disagreement between a wallet’s pending label and a confirmed explorer transaction without submitting a duplicate swap.
Understand what a failed preflight estimate is warning about and why entering a manual gas limit may not fix a swap.
Diagnose device connection and signing failures without exposing the hardware wallet’s recovery phrase.
Trace the assets that actually left and entered your account without double counting router and pool transfers.
Identify whether your confirmed transaction granted a token allowance or actually exchanged tokens, then resume the correct step.
Determine whether repeated swap clicks created duplicate requests, same-nonce replacements or two independently executable trades.
Distinguish a consumed permit nonce from the wallet account’s transaction nonce when a signed authorization stops working.
Use the transaction hash, block inclusion and receipt to distinguish a waiting swap from a reverted or unsubmitted request.
Collect useful evidence when an explorer reports execution reverted without decoding a clear reason.
Identify whether a missing route reflects token identity, unsupported execution or insufficient liquidity for your exact request.
Check confirmed and replaced transactions before treating a nonce-too-low message as a reason to submit another swap.