USDHow to Check Liquidity of a Crypto Before You Buy or Swap
You’re about to buy a token and the chart looks fine, but that doesn’t tell you if you can actually get out later. Liquidity is what decides whether a “$5,000 trade” fills like a normal order or turns into a mess of slippage, failed swaps, and price impact. The good news: you can check liquidity in a few minutes using order books, pool depth, and basic on-chain sanity checks.
TL;DR
- You’ll be able to estimate if a token can handle your trade size without ugly slippage.
- The checks take ~5–15 minutes per token once you know where to look.
- Most people only look at volume/market cap and miss thin order books or tiny LP pools.
Liquidity is the difference between “I can buy and sell whenever I want” and “I’m stuck unless I accept a terrible price.” It’s also the difference between a swap that confirms normally and one that reverts because price moved a fraction of a percent. If you’re trying to avoid getting trapped in a low-liquidity coin, you need to look at where the token trades (CEX order books vs DEX pools), how much depth is actually there, and whether that liquidity is real and accessible.
What you need before you start
You don’t need a paid terminal, but you do need to know where the token trades and what chain it’s on.
If the token is mainly on a centralized exchange (CEX), you need access to that exchange’s trading page (even without depositing) so you can view the order book and recent trades.
If the token is mainly on a DEX, you need:
A wallet that can read the chain (MetaMask for EVM chains, Phantom for Solana, etc.). You don’t have to connect it to anything to do the checks, but it helps you confirm the correct token contract.
The token’s contract address (or mint address on Solana). Names and tickers are unreliable; liquidity checks are meaningless if you’re looking at the wrong asset.
A block explorer for the chain (for EVM: Etherscan-style explorers; for Solana: Solscan-style explorers). You’ll use it to confirm the contract and spot obvious red flags.
A DEX analytics view or the DEX’s own pool page so you can see pool reserves and (ideally) depth around the current price. You’re not trying to be perfect; you’re trying to avoid the “looks liquid until you trade” trap.
Step-by-step
Confirm the exact token: Find the token’s contract address from the project’s official site, official docs, or a verified social profile, then cross-check it in a block explorer to make sure it’s the same address the market you’re looking at is using. This matters because fake tokens often copy the name and ticker, and they can even have “liquidity” in a scam pool that’s irrelevant to the real asset. Before moving on, verify the contract address matches across the explorer and the exchange/DEX market page, and that you’re on the correct network.
Identify where liquidity lives: Decide whether the token’s real liquidity is on a CEX order book, a DEX pool, or split across both, because the measurement is different in each place. A token can show a decent crypto price and even a respectable coin market cap, but if most trading happens on one venue you don’t use, your practical liquidity is lower than it looks. Before moving on, list the top one or two venues you would actually trade on (the ones you can access and withdraw from), not just “where it’s listed.”
Read the order book depth (CEX): On a CEX market page, look past the last traded price and focus on the order book: how many units are sitting on the bid side (buyers) and ask side (sellers) close to the mid-price. Liquidity here means “how much can I sell without walking the price down” and “how much can I buy without pushing it up.” Before moving on, check whether the top levels are thick and continuous or thin and gappy; gaps are where your market order jumps levels and your fill gets worse than expected.
Estimate slippage with a test size: Pick a realistic trade size (what you’d actually buy/sell) and mentally “consume” the order book levels until you reach that size, then compare the average fill price to the mid-price to estimate price impact. This matters because a token can look fine for $100 trades and be a disaster for $5,000 trades. Before moving on, decide what your maximum acceptable slippage is for that token and that venue, and don’t assume you can fix it later with a tighter setting if the depth just isn’t there.
Check DEX pool reserves (DEX): If the token trades on a DEX, open the pool page and look at the reserves (how much of token A and token B are in the pool). In constant-product AMMs, shallow reserves mean your trade moves the price more, which is why low-liquidity pools punish larger swaps. Before moving on, confirm you’re looking at the correct pool (correct token address and correct pair) and that the pool isn’t a weird, illiquid pair that only exists to bait swaps.
Look for concentrated liquidity reality: On DEXs that use concentrated liquidity, the headline “TVL” or total liquidity can be misleading if most liquidity is placed far away from the current price. What matters is liquidity in-range near the current price, because that’s what your swap actually trades against. Before moving on, check whether the pool view shows depth around the current price (some interfaces show a depth chart or liquidity distribution); if liquidity is mostly out-of-range, treat it like a thin pool even if the total number looks big.
Sanity-check on-chain activity: Use the block explorer and the DEX analytics view to see whether there are regular swaps, a reasonable number of holders, and a distribution that doesn’t look like one wallet controls everything. This isn’t a “liquidity metric” by itself, but it tells you whether the liquidity you see is likely to be usable when you need it. Before moving on, check that swaps are happening across time (not just one burst), and that the pool isn’t dominated by a single LP position that could be pulled without warning.
Cross-check against market-wide context: Compare what you found to the token’s broader footprint: where it sits in a crypto price index view, whether its coin market cap makes sense relative to how much real depth you saw, and whether the “crypto price” is consistent across venues. This matters because big discrepancies often mean fragmented liquidity, withdrawal issues, or a price that’s being set by a thin venue. Before moving on, confirm you can both enter and exit on the same venue (or have a realistic bridge/transfer plan) without relying on a perfect arbitrage that may not exist for small tokens.
What goes wrong
You checked the wrong token contract
- Symptom: The DEX pool looks liquid, but the token you bought can’t be sold on the main markets (or the ticker doesn’t match what others trade).
- Fix: Re-do the check using the contract address from official project channels, then verify the pool/market uses that exact address before trading.
Order book looks “busy” but depth is thin
- Symptom: Lots of tiny orders and frequent prints, but your trade moves the price hard or fills in chunks at worse levels.
- Fix: Ignore the tape and measure cumulative depth within a tight band around mid-price; if depth isn’t there, reduce size or don’t trade there.
DEX TVL looks high but swaps still slip
- Symptom: The pool shows a big liquidity/TVL number, yet even moderate swaps cause large price impact.
- Fix: Check whether liquidity is concentrated out-of-range; use a pool view that shows depth near the current price and treat out-of-range liquidity as effectively unavailable.
You used the wrong pool or wrong pair
- Symptom: You see a pool with decent reserves, but the price is off compared to other venues or the token route is strange.
- Fix: Find the primary pool used by most traders (often the one paired with the chain’s main asset or a major stablecoin) and confirm the contract addresses match.
Liquidity disappears when you need it
- Symptom: You could buy fine, but later sells revert, slippage explodes, or the pool becomes extremely thin.
- Fix: Check whether liquidity is controlled by a small number of LPs; avoid relying on a single pool, and consider splitting orders or using limit orders where possible.
Pending or failing swaps confuse the diagnosis
- Symptom: Your swap sits pending or fails, and you can’t tell if it’s liquidity or network conditions.
- Fix: Look at the transaction in a block explorer: if it reverted due to slippage, that’s liquidity/price movement; if it’s just pending, you may need to speed up/replace the transaction or wait for congestion to clear.
Approval risk after checking/trading
- Symptom: You approved a token spend for a router, then later worry about lingering permissions.
- Fix: Revoke or reduce token allowances using a reputable allowance management tool for your chain, especially after interacting with unfamiliar routers.
When this isn't the right move
If you’re planning to trade a size that’s large relative to the visible depth (order book or in-range pool liquidity), “checking liquidity” won’t make the trade safe; it just tells you the bad news earlier. In that case, your better move is to use a venue with deeper liquidity, split the order over time, or use limit orders (CEX, or a DEX limit solution) so you control the worst acceptable price.
If you can’t verify the token contract cleanly, stop. Liquidity analysis on the wrong contract is worse than useless because it gives you confidence in a market you’re not actually trading.
Tools and references
https://etherscan.io
