Swapping one crypto asset for another on a decentralized exchange sounds simple, but the price you see is not always the price you get. This guide explains slippage and sandwich bots in plain English, and shows practical ways to limit how much extra you might pay on a trade.
When you submit a swap on a decentralized exchange, you usually see a quoted output amount before you confirm. That quote is based on the current state of the liquidity pool. By the time your transaction is included in a block, other trades may have changed the pool's balances, so the actual output can be higher or lower than the quote. The gap between expected and actual output is slippage. It happens in traditional markets too, but onchain swaps make it visible directly in the interface. Slippage is not a fee charged by the exchange. It is simply the result of trading against a pool whose prices change as trades occur.
A sandwich bot is an automated program that scans the mempool, the waiting area for pending transactions, looking for swaps large enough to move the price. When it finds one, it submits two transactions: one just before yours and one just after. The first trade buys the token you are buying, pushing the price up. Your trade then executes at that higher price. The bot immediately sells the token it bought, capturing the difference. Your swap is effectively sandwiched between the bot's two trades.
Because pending transactions are public on many blockchains, the bot does not need your wallet address or private information. It only needs to see that a swap is waiting and estimate that the price movement will cover its own costs and leave a profit. Some bots operate continuously, while others trigger only when a pending trade crosses a size threshold. The effect on your wallet is similar either way: you receive less of the output token than the quote suggested.
Most swap interfaces include a slippage tolerance setting. This tells the smart contract the maximum price change you will accept. If the market moves beyond that limit, the transaction reverts and no swap occurs. Setting the tolerance too wide gives a sandwich bot more room to profit from your order. Setting it too narrow can cause repeated failures, and each failed attempt can still consume network fees.
There is no single tolerance that works for every token. A swap between two stablecoins usually has different price behavior than a swap involving a newer or less liquid token. Match the setting to the specific pair and current conditions rather than copying a number from a forum or social media post. Wallets and interfaces may display a warning if your tolerance is set unusually high for the pair you are trading. Treat that warning as a prompt to review your settings, not as a directive to proceed.
You cannot remove slippage or sandwich bots entirely, but you can limit their effect on your trades. If you are new to a token pair, consider starting with a small amount to observe how the interface handles quotes and execution before committing to a larger swap. None of these steps promise a specific result. They simply reduce the opportunities for your transaction to be seen and reordered before it settles.
Market volatility often increases the distance between a quoted price and the final execution price. On 2026-11-20, VaultX's incident desk reported that Anthropic's Nasdaq debut closed 17% above its offer price while Bitcoin slid. The same day, the total crypto market cap fell 4.9% to $2.14T, and the Fear & Greed index sat at 12, in Extreme Fear territory.
When prices are swinging sharply, a quote can become stale within seconds. A swap that looked acceptable when you submitted it may execute at a materially different rate, particularly if the token pair has limited liquidity. Reviewing current market conditions before trading helps you set realistic expectations; it does not predict where prices will go next. The same volatility that moves crypto prices can also affect traditional assets, as seen when Anthropic's IPO moved while crypto markets slid. Each market has its own liquidity profile, so slippage behavior can differ even on the same day.
Common mistakes include copying slippage settings from social media without checking the token pair or pool size, overlooking failed transaction fees, confusing the exchange fee with price impact, and leaving a transaction pending for a long time without a deadline. Checking the status of a pending transaction on a block explorer can tell you whether it is still waiting or has already been replaced by a higher-fee transaction.
Everything in this article is tracked live and free on VaultX.
Open the live viewGet alerts on TelegramSlippage is the difference between the price you expect when you submit a swap and the price at which the trade actually executes. It happens because market prices move while your transaction is being confirmed. Small price differences are normal, but large ones can make a trade more expensive than expected.
A sandwich bot detects a pending swap, places its own trade immediately before yours to push the price in a favorable direction, and then sells right after your trade executes. You end up with a worse execution price, and the bot captures the difference. This is possible because pending transactions are visible on many public blockchains before they are finalized.
You cannot fully eliminate the risk on a public blockchain, but you can reduce exposure by using smaller trade sizes, appropriate slippage tolerances, deadlines, and platforms that offer MEV protection or private routing. No setting guarantees you will avoid all price impact.
Written by an AI agent from public data and reviewed by automated checks. Educational only, not investment advice.