An Ethereum decentralized-exchange (DEX) swap can deliver less than its quote for three separate reasons: the trade itself moves the pool price, the market changes while the transaction waits for inclusion, or transaction ordering exposes the swap to adverse maximal extractable value (MEV), such as a sandwich trade. A lower slippage tolerance can reject a transaction that moves too far, but it cannot force the quoted price. Understanding which mechanism is responsible is the first step toward choosing a sensible trade size, route and protection setting.
What this explanation covers
Here, “Ethereum trade” means a token swap on an Ethereum-based decentralized exchange, especially an automated market maker (AMM). A centralized exchange uses an order-matching system with different mechanics, and the available evidence does not establish that the explanations below apply to those venues.
As an Amazon Associate I earn from qualifying purchases.
On a DEX, your wallet usually signs a transaction that interacts with one or more liquidity pools. The interface shows a quote before you submit it, but the blockchain may include the transaction later. The amount finally received is therefore determined by pool conditions and transaction ordering at execution time, subject to the limit you selected.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Price impact and slippage are different
People often use “price impact” and “slippage” interchangeably, yet they answer different questions. The Uniswap Protocol Glossary defines price impact as “the difference between the mid-price and the execution price caused by your trade size relative to the pool’s liquidity.” It defines slippage as “the total difference between the expected price at the time of submitting a transaction and the actual execution price.”
#1 Best Overall
| Term | What creates the difference | When it is measured | What a trader should infer |
|---|---|---|---|
| Price impact | Your order changes the pool price because its size is large relative to available liquidity. | Comparing the pool’s mid-price with the execution price caused by your trade. | Splitting a large swap, finding a deeper pool or using a different route may reduce this component. |
| Slippage | The total gap between the expected submission-time price and the final execution price. It can include price impact, intervening market moves and ordering effects. | From quote or submission to on-chain execution. | A tolerance is a limit on how adverse the final result may be accepted, not a promise of the quote. |
A swap can have low price impact but still experience slippage if the market moves while the transaction is pending. Conversely, a rapidly executed swap can suffer substantial price impact even when the broader market has not moved. Keeping those causes separate prevents you from trying to fix a liquidity problem by changing a time-based setting, or treating a market move as evidence that the pool calculation was wrong.
How an AMM produces the quoted price
Reserves, not a headline volume number
An AMM prices a swap from the tokens held in a particular pool and the protocol’s pricing rule. The pool’s reserves determine how much of the output token is available at successive prices. A 24-hour volume figure describes past activity; it does not reveal the executable depth at your chosen price and exact moment. Two pools can show similar volume while offering very different outcomes for your trade size.
The constant-product example
Uniswap’s v2 documentation describes the constant-product model: the product of the two reserves is maintained, so withdrawing one token requires depositing the other. In simplified form, if reserves are x and y, the pool seeks to preserve x × y = k (before accounting for the protocol’s fee treatment). Taking a meaningful amount of y out leaves more x in the pool, changing the reserve ratio and making the next unit of y more expensive. The larger your withdrawal relative to the reserves, the farther the average execution price moves from the starting mid-price.
This is a v2 description, not a complete model of every current Uniswap version; the v2 page notes that v4 is current. Other pools and versions can use different curves, fee rules or concentrated-liquidity ranges. The general principle remains: the available liquidity at the prices your route crosses determines the execution result. See Uniswap v2 Pricing and How Uniswap Works for the documented mechanics.
Rank #2
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
Why route choice changes the result
A DEX aggregator or interface may quote a direct pool, a multi-hop path or a split across pools. A path with more total liquidity can reduce price impact, but each additional hop introduces another pool price, fee and execution dependency. The displayed output is the route’s estimate, not a guarantee that every pool will be unchanged when the transaction executes.
Why the quote can change before mining
The quote is a snapshot
When you request a quote, the interface reads current pool and market data. Your signed transaction then enters a queue and waits to be included in a block. During that interval, other swaps can alter the reserves, and the external market can move relative to the quoted pair. A transaction submitted with an apparently attractive output can therefore execute at a different rate even if nobody deliberately targets it.
The Uniswap explanation of slippage describes this time gap and the role of a user-selected tolerance. If the price moves beyond the permitted range, the swap may fail rather than execute at an unacceptable output. If the movement remains inside the range, the transaction can succeed at a worse price than the original display.
Pending transactions can be visible
On public transaction infrastructure, a pending swap may be visible to participants who monitor transactions before block inclusion. Visibility matters because the order in which transactions execute can change the pool price that your swap encounters.
How MEV and sandwich trading worsen execution
Ethereum.org defines maximal extractable value (MEV) as value associated with controlling transaction inclusion and ordering. In a sandwich pattern, a searcher places a trade before a large user swap, moving the pool price, and then trades after the user’s swap. The user’s own transaction still executes according to the pool’s rules, but at a less favorable point on the curve. Ethereum.org states: “Users who are sandwiched face increased slippage and worse execution on their trades.” Read the full explanation in Ethereum’s MEV documentation.
The important distinction is causality. Your order creates some price impact simply by consuming liquidity. A sandwich trader can add an adverse price movement immediately before your order and unwind after it. A transaction that reaches the stated minimum output can therefore be successful while still reflecting a worse price than the initial quote.
MEV is not limited to a single pattern, and not every disappointing swap was attacked. A normal intervening trade, a volatile market or a thin pool can produce a similar symptom. Establishing a sandwich requires transaction-level analysis; the amount received alone does not identify the cause.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesWhat slippage tolerance actually controls
It sets an execution bound
When you choose a slippage tolerance, the transaction encodes the least output (for an exact-input swap) or the most input (for an exact-output swap) you are willing to accept under the interface’s rules. The tolerance is a boundary around the quote. It does not reserve liquidity, freeze the pool price or make the quote achievable.
Rank #4
Lower tolerance: more protection, more failures
A tight tolerance rejects a transaction if intervening trades, market movement, price impact or ordering effects push the result outside the allowed range. You may need to submit again, perhaps with a refreshed quote. This limits how bad a successful execution can be, but repeated failures can cost network fees where a transaction has already been processed far enough to incur them, depending on the implementation and venue.
Higher tolerance: fewer failures, wider downside
A wider tolerance makes inclusion more likely during volatile conditions or when the route is changing, but it authorizes a more adverse outcome. If a sandwich or other price move occurs, the transaction can still succeed up to that wider limit. A successful swap at the tolerance limit does not mean the original quote was preserved; it means only that the encoded bound was respected.
There is no universal setting established by the available documentation. The appropriate bound depends on the pair’s volatility, pool depth, trade size, route and how much execution uncertainty you are willing to accept.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →A practical way to diagnose a worse-than-expected swap
- Record the quote and transaction terms. Note the quoted output, minimum output or maximum input, route, fee information shown by the interface and the tolerance. Keep the transaction hash so the executed amounts can be checked on-chain.
- Compare trade size with pool reserves. If your input is substantial relative to the relevant pool’s reserves, the trade itself likely created material price impact. A high 24-hour volume number does not disprove this; inspect the liquidity available along your actual route.
- Check the delay. Compare the quote time, submission time and block-inclusion time. A long pending interval gives other swaps and the wider market more opportunity to move the executable price.
- Inspect the route and intermediate pools. Multi-hop or split routes can encounter a changed reserve balance in any leg. One shallow leg can dominate the final result even when another leg is deep.
- Look for ordering around your transaction. An immediately preceding trade in the same pool that moves the price in the direction harmful to you, followed by a reversing trade after yours, is consistent with a sandwich pattern. It is evidence to investigate, not proof from the output alone.
- Check whether the transaction reached its bound. If the received amount is close to the minimum output, the swap used most of the adverse movement your tolerance allowed. If it failed, the bound worked as a rejection condition; it did not indicate that the quote was executable at that moment.
Ways to reduce adverse execution
Reduce the trade’s own price impact
- Trade an amount that is smaller relative to the available reserves.
- Consider splitting a large order when the interface and fee structure make that practical; splitting can reduce the movement caused by each leg, although later legs face whatever the market and pools do in the meantime.
- Compare routes and pools for executable depth, not just displayed volume. A route with more usable liquidity may offer a better average price even if its quoted path is more complex.
Control the time-related component
Refresh the quote immediately before signing, and avoid treating a stale screen as a firm offer. During unusually fast markets, a tolerance that is too tight may cause repeated failures; a tolerance that is too wide may accept an outcome you would not choose manually. Decide which risk matters more for this transaction before submitting it.
Best Value
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
Consider private or intent-based execution paths
Uniswap Labs describes private routing in Uniswap Wallet and UniswapX, where fillers compete to execute user intents, as approaches intended to reduce some harmful MEV exposure or return value through competition. These are vendor-described risk-reduction approaches, not guarantees that a swap will receive the best possible price or avoid every form of MEV. Details are in Uniswap Labs’ explanation of MEV.
When comparing an execution option, ask five concrete questions:
- Does it merely set a minimum-output bound, or does it change the routing and transaction-order path?
- What happens if the desired execution cannot be found: does the transaction fail, or can it fill at a wider range?
- Is the transaction exposed to a public pending pool?
- Which pools and route depth are available for this pair and size?
- Is the stated protection a documented guarantee, or an intended reduction in a particular risk?
Common mistakes that lead to bad conclusions
- Calling every difference “slippage.” Price impact is the portion caused by your own size; slippage is the total submission-to-execution difference.
- Assuming a large volume badge means deep liquidity. Historical turnover does not specify reserves available at your price.
- Setting an extremely high tolerance to prevent failure. This trades a visible rejection for permission to accept a much worse execution.
- Assuming success means the quote was guaranteed. A successful transaction can execute anywhere inside the permitted range.
- Blaming MEV without checking the transaction sequence. Sandwiching is one possible ordering pattern, not the explanation for every unfavorable fill.
- Applying v2 equations to every pool without qualification. The constant-product description is useful for v2; current and other versions can differ in curve and liquidity design.
The decision in one sentence
If the loss comes mainly from your order’s size, seek deeper or differently routed liquidity; if it comes from waiting and market movement, use a bound that reflects your failure-versus-downside preference; if transaction ordering is the concern, consider a documented private or intent-based route while treating its protection as risk reduction rather than a promise.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
