Skip to main content
Menu

⚠️ Risk Warning: Trading forex, CFDs, and cryptocurrencies involves substantial risk of loss and may not be suitable for all investors. This platform provides educational content only and does not constitute financial advice.

◎ Level 3 · Intermediate Market Structure & Exchanges Decentralised Exchanges (DEX)

Price Impact on DEX Trades

Understand how your own DEX trade moves the execution price, why price impact grows non-linearly with trade size, and how pool design, routing and MEV can

Progress 0%

Reading progress — saved on this device

Risk first: Price impact can increase sharply when active liquidity is thin or concentrated away from the current price. A quoted route can also deteriorate before settlement. Treat the quote as conditional, verify slippage settings, and do not confuse price impact with network fees or a general market forecast.
Standalone building blockEducational onlyLast reviewed: 21 August 2026

Core concept

Price impact is the change in execution price caused by the trade itself. On an automated market maker (AMM), a swap changes the pool reserves or consumes liquidity across price ranges; on an order-book DEX, a sufficiently large marketable order consumes multiple price levels. The larger the trade relative to available liquidity, the larger the impact tends to be.

Key distinction: price impact is not the same as slippage tolerance. Price impact is an economic consequence of consuming liquidity. Slippage tolerance is a transaction-protection setting that defines how far the execution may move before the transaction reverts or fails.

How the mechanics fit together

Trade size
Notional relative to active liquidity.
Liquidity curve / depth
Reserves, ticks, ranges or order levels are consumed.
Average execution price
The fill differs from the pre-trade reference price.
Effective cost
Impact combines with fees, MEV and quote movement.

For a simple constant-product AMM, x × y = k. Buying one asset reduces its reserve and increases the reserve of the asset paid in, pushing the marginal price against the trader. The relationship is non-linear: doubling trade size can more than double price impact when the trade becomes large relative to reserves.

DriverWhy it matters
Trade size / pool depthThe central ratio. Large orders against shallow active liquidity create larger impact.
Concentrated liquidityHeadline TVL can overstate liquidity available near the current price if capital sits outside the active range.
Route and number of hopsAggregators may split or multi-hop a trade. Better routing can reduce impact, but each hop can add fees or contract risk.
MEV and sandwich riskPublic mempools can allow adversarial ordering that worsens the realised execution beyond the static quote.
Volatility / quote agePool state can change between quote and inclusion, making the original estimate stale.

Evidence to inspect

  • Quoted output and minimum received: separate the route's estimated execution from the user’s slippage-protection threshold.
  • Active liquidity, not only TVL: for concentrated-liquidity AMMs, inspect liquidity around the current tick/range.
  • Route composition: note pools, fee tiers, intermediate tokens and whether the order is split across venues.
  • Price-impact estimate methodology: interfaces may use different reference prices or include/exclude LP fees.
  • Recent block conditions: volatility, pending transactions and gas congestion can affect quote freshness and MEV exposure.
  • Independent simulation: where practical, compare another router or a direct-pool quote before a high-value swap.
Do not compare percentages blindly: one interface may report price impact excluding LP fees while another folds more costs into a single headline number.

Practical workflow

  1. Confirm the token contract addresses and network before analysing the quote.
  2. Record the input amount, quoted output, route, LP/venue fee and stated price impact.
  3. Compare the trade notional with active liquidity or executable depth around the current price.
  4. Check whether splitting the order materially improves expected execution after extra fees and timing risk.
  5. Set a slippage tolerance appropriate to the asset and conditions; do not simply widen it to force a trade through.
  6. For larger trades, compare multiple routes or use protected/private execution where available and appropriate.
  7. After settlement, compare the realised output with the pre-trade quote and retain the transaction hash for review.

Worked example / thought exercise

Scenario: a constant-product pool contains 2,000,000 USDC and 1,000 ETH, implying a spot reference of 2,000 USDC per ETH. Ignore fees for the moment.

A trader wants to remove 10 ETH. To preserve x × y = k, the ETH reserve falls to 990 and the USDC reserve must rise to about 2,020,202. The trader therefore pays about 20,202 USDC for 10 ETH, an average of roughly 2,020.20 USDC per ETH.

The average execution is about 1.01% worse than the pre-trade 2,000 reference before LP fees, gas and any MEV. A larger trade would create disproportionately more impact.

Question: if an aggregator finds two pools with independent liquidity, why might splitting the order reduce impact even if the total notional is unchanged?

Common mistakes and misunderstandings

Confusing price impact with slippage tolerance

A 1% slippage setting does not mean the trade has 1% price impact. The setting is a protection threshold; impact is produced by the trade and liquidity state.

Using total TVL as executable liquidity

In concentrated-liquidity pools, much of the capital may sit outside the current price range and contribute little to the immediate trade.

Widening tolerance to fix a bad quote

A wider tolerance can increase exposure to adverse price movement and sandwich attacks. It does not create deeper liquidity.

Ignoring multi-hop and MEV costs

A route with lower static pool impact can still deliver a worse realised result after additional fees, quote decay or adversarial ordering.

Knowledge checkpoint

  1. A DEX shows 0.7% estimated price impact and you set 2% slippage tolerance. What does each percentage mean?
  2. Why can a pool with high TVL still produce large price impact for a particular swap?
  3. If two routes show similar quoted output, which route-level risks would you compare before executing?

FAQs

❓ Does a larger slippage tolerance reduce price impact?

No. It only permits a wider execution range before the transaction reverts. The underlying price impact is determined by the trade size and available liquidity.

❓ Why does price impact rise faster for larger AMM trades?

AMM pricing curves are non-linear. As a trade consumes reserves or concentrated liquidity, each additional unit is executed at a progressively less favourable marginal price.

❓ Can an aggregator eliminate price impact?

No. It can search and split across available liquidity to reduce impact, but it cannot create liquidity that does not exist.

❓ Is price impact the same as the difference between a DEX and CEX price?

No. Cross-venue price differences can reflect basis, latency or fragmentation. Price impact specifically refers to the price movement or execution deterioration caused by the trade itself.

📋 Summary

Price impact is the execution deterioration caused by consuming liquidity. It grows with trade size relative to active depth and depends on AMM curves, concentrated ranges, route design and market conditions. Analyse it separately from slippage tolerance, LP fees, gas and MEV; for larger swaps, compare routes and active liquidity before execution.

BUILD YOUR OWN PATH

Want this in a personalised order?

Take the crypto assessment and get a custom path of 10 modules matched to what you already know. Free, no card required.

Build my path →