A successful swap can deliver fewer tokens than the quote because a quote estimates output; the transaction settles against the pool’s state when it is included.
Why did my confirmed swap pay less than the quote?
Your swap succeeds as long as its actual output meets the transaction’s minimum received amount, also called amountOutMin. Output below that limit makes the swap revert. Output between the minimum and the quote counts as success, even when the difference feels large.
The most common cause is price movement between the quote and inclusion. A trade that changes the pool’s token reserves changes its price; when your swap executes against those new reserves, it can return less. Slippage tolerance sets how much the output may fall before the swap reverts. On Etherscan, compare the swap event’s actual amounts in and out with the quote and minimum received shown by your wallet or DEX.
A sandwich attack can also push your fill close to its minimum. A bot trades ahead of your swap in the same pool, moving the price against you, then trades after it to capture value from the price movement. Those surrounding trades are the tell: look for bot transactions in the same pool immediately before and after yours. A Flashbots sandwich check can help establish whether those trades explain your lower output. Flashbots Protect can reduce exposure to this public-mempool sandwich route on a future swap.
Fees can reduce what reaches your wallet, too. A DEX interface fee may send a slice of the output to a separate fee address; look for that transfer alongside the pool’s output. A fee-on-transfer token takes a tax when tokens move. In that case, the pool may send one amount while your wallet receives less. Compare the swap event and pool transfer with the token transfers to your wallet and any fee address to tell these causes apart.
If the transfer list does not match any of those patterns, inspect the full transaction’s token transfers and swap events on Etherscan. The event records the actual amounts exchanged, while the transfer list shows where the tokens moved afterward. Confirm the token contract and the transaction’s input and output assets before drawing a conclusion.
Can I get the missing tokens back?
Usually, no: a confirmed swap cannot be reversed, and a fee or token tax has already been applied. If the transfer list shows an unexpected fee address or transfer, save the transaction hash and ask the DEX or token team to identify it.
Why did the quote change before I confirmed?
The interface refreshed its estimate as the pool price or available liquidity changed. A quote can move while you review it; the confirmed transaction uses its own minimum received limit when it executes.
Next time, review the minimum received before signing, choose a slippage tolerance that fits the token’s behavior, and consider Flashbots Protect to reduce sandwich exposure.
- Open the confirmed transaction on Etherscan.
- Compare its swap event with pool, fee-address, and wallet transfers.
- Match the trace to price movement, a sandwich, an interface fee, or a token tax.
- Set an appropriate minimum received and use Flashbots Protect when submitting next time.
Questions about preventing a smaller fill
How tight can slippage be before swaps start failing?
Set tolerance just above the price movement you expect during confirmation. Tighter tolerance limits the output reduction you accept, but the swap reverts if the pool moves enough to put output below minimum received. Volatile or thin pools may need more room than deep, stable ones.
Does Flashbots Protect refund value lost to price drift?
No. Flashbots Protect can reduce exposure to public-mempool sandwich attacks, but it does not refund losses from ordinary price movement, interface fees, or token taxes. Your minimum received still controls the lowest output your swap accepts.
What is the difference between price impact and slippage?
Price impact is the effect your trade size has on the pool price as it executes. Slippage is the difference between an expected price or output and the result at execution, including changes while the transaction waits. Both can lower output, but slippage tolerance sets the limit that triggers a revert.
How can I check a token’s transfer tax before buying?
Review the token’s documentation and contract, then inspect recent buys and sells on Etherscan. Compare the amount sent by the pool with the amount received by a wallet. A consistent gap can indicate a transfer tax; test only with an amount you can afford to lose, since taxes and token rules may vary by transaction.