A $1,000 swap can move a shallow pool’s price by about 20%, even before fees. If your Base token swap is pending or failed, a wide spread may explain the poor quote or a failed price check—but a pending transaction needs a separate check.
Pool depth explains why the quote looks wide
In a V2 liquidity pool, the price shifts as your trade changes the amounts of each token in the pool. Uniswap’s V2 documentation describes this with the formula x × y = k: the pool’s token balances multiply to a value that trades must preserve, apart from fees.
Consider two example pools, each priced at $1 per token before a trade. One holds 100,000 tokens and $100,000; the other holds 5,000 tokens and $5,000. A $1,000 buy would receive about 990 tokens from the deeper pool, but only about 833 from the smaller one, before fees.
That difference is price impact: how much your trade moves the pool price. A wide spread can describe the gap between the price to buy and sell, while price impact describes how your trade changes its execution price. They are related, but a failed swap can also reflect the price changing while it waits. BaseSwap is a decentralized exchange on Base, where pool depth matters when swapping tokens; the BaseSwap app is a way to explore that activity.
A pending swap and a failed swap need different checks
A pending transaction has been submitted but has not finished. Its eventual quote can change as other swaps trade against the pool. A failed transaction has finished without making the swap, often because the output fell below the minimum amount allowed by the slippage setting—the permitted price movement—or because its deadline passed.
For a pending attempt, look up its transaction hash in a Base block explorer and check whether it is still pending, confirmed, or reverted. Base uses a sequencer to order transactions, as Base’s documentation explains, so a delay alone does not tell you whether the pool price caused the problem. Avoid submitting the same swap again until you know what happened; if the first one confirms, a duplicate could trade twice.
For a failed attempt, read the transaction result and get a fresh quote. Compare the expected output with the minimum output, which is the least the swap will accept. If the quote is still poor, try a smaller amount or choose a deeper pool or route if one is available. Raising slippage can let a trade through at a worse price, so it does not fix thin liquidity.
Check the pool before retrying
A small pool can show a sharp price move from a modest trade, especially when few tokens are available on one side. A large displayed balance is not enough by itself: check how much is available around the price you expect, and compare the quote for your trade size with a smaller one.
BaseSwap can be one place to check Base token pools before deciding whether to retry. My practical tip: if the smaller test quote is much better, reduce the trade size and review the fresh minimum output before signing.
Top comments (0)