Why your volume is not showing on DexScreener

DexScreener indexes pools, not tokens

This is the single fact that explains most missing-volume reports. A screener does not watch your mint address and add up everything that happens to it. It watches liquidity pools it recognises, decodes the swap instructions inside those pools, and prices them against the quote asset. A token page is just an aggregation of every pool the indexer has found for that mint.

Three consequences follow, and each of them produces a different flavour of "my volume is missing":

• If a pool exists but the indexer has not picked it up yet, the swaps happened, cost real SOL, and appear nowhere.
• If your token trades across several pools, the volume is split across several pair pages. The pair page you have open may genuinely show a small number while the token page shows the real total.
• If a swap is routed through an aggregator, it still executes against an underlying pool, so it lands on that pool's page rather than on any page belonging to the aggregator.

Before assuming something failed, open the token-level page rather than a single pair, and check how many pairs are listed for the mint.

Eight reasons the number stays low or at zero

1. The pool is too new. Indexers discover new pools on a delay. Minutes, usually, but a freshly created pool during a busy period can lag longer. Swaps executed in that gap are backfilled on some venues and simply lost on others.
2. The program is not supported. Solana has far more swap programs than any screener decodes. Newer or niche venues can be invisible for weeks. This is the most common cause when someone routes through an exotic venue to save on fees.
3. You are looking at the pre-migration pair. A launchpad token trades on a bonding curve first and on a standard pool after it graduates. These are two different pairs with two different pages. Volume does not carry over. The Pump.fun mechanics guide covers exactly where that handoff happens and what breaks around it.
4. Liquidity is below the display threshold. Pairs with negligible liquidity are frequently hidden from lists and filters even when the pair page itself exists. The activity is recorded; nobody browsing will encounter it.
5. The quote asset is unpriced. A pool quoted against an obscure token rather than SOL or a stablecoin gives the indexer no reliable price to convert with, so the USD volume column can read as a fraction of reality.
6. Swaps are too small to matter in aggregate. Two hundred swaps of 0.01 SOL is two SOL of volume. It is real, it is correctly displayed, and it is invisible. This is a sizing problem, not an indexing one.
7. Transactions failed. Failed swaps still burn the base fee and the priority fee. They produce no volume because no swap occurred. Slippage set too tight during a volatile minute is the usual cause, and the wallet balance drops in a way that looks like the trades went through.
8. You are on the wrong pair entirely. Duplicate mints with near-identical names and symbols are routine. Verify the mint address character by character, not the ticker.

The five-minute checklist

Work through this in order. It resolves the large majority of cases without needing anyone's support desk.

If every transaction succeeded and the pool is indexed, the volume is there. What remains is a question about size and timing, not about whether the system worked.

Your campaign window versus the 24-hour column

People compare a three-hour campaign against a rolling 24-hour figure and conclude that something is broken. Nothing is broken; the two numbers describe different things.

The headline volume on most screeners is a rolling window that keeps moving. Volume you generated four hours ago is still in the 24-hour figure and has already left the one-hour figure. If you spend a fixed budget evenly across a full day, every short-window column stays small and none of the activity-sorted lists ever notice you. The same budget concentrated into the hours when the audience is awake produces a short-window figure several times higher, which is what ranking and trending surfaces actually read.

This is why density matters more than the total, and it is the reason the console asks for a shape as well as an amount. The sizing guide walks through deriving the target from the board you are competing on rather than from a number somebody quoted you.

Showing volume and trending are different problems

A token can display an entirely healthy volume figure and still appear on no list anyone browses. Trending placement is not a pure function of volume. Depending on the surface it blends recent trade count, unique participating wallets, buy and sell balance, liquidity depth, price movement and how recently the pair was created, and the exact weighting is not published anywhere.

Practical consequence: a campaign built from a small number of large swaps can produce a good volume number and a poor trade count, while the same budget split into many smaller swaps across many wallets produces the same volume with far better unique-address and trade-count figures. If your goal is a discovery surface rather than a headline number, optimise for the second shape. Our measurement notes describe which of these figures we read on-chain and which ones we refuse to claim precision about.

When the volume is real but the chart looks wrong

Two more cases are worth naming because they get misreported as missing volume.

Flat candles with rising volume. This is the expected outcome of balanced buy and sell flow. Volume bars grow, price does not move much. If you wanted price movement you wanted buy pressure, which is a different instrument with a different risk profile and a chart that the next real seller has to sell into.

Volume that appears and then partly vanishes. Screeners recompute windows and occasionally reindex. A figure that looks slightly different an hour later is normal. A figure that halves permanently usually means you were reading a single pair page while routing spread across two pools.

If you want to see the shape before committing money, the console on the home page shows the estimated swap count, wallet spread and exact SOL fee for a given target before anything is submitted, and the venue detection tells you which pools your token actually has.

One thing worth doing first

Open a single successful transaction from your campaign in an explorer and read the inner instructions. You will see the program that executed the swap, the pool it hit and the amounts on both sides. Almost every "the volume is not showing" question is answered in that one screen, and the answer is usually either an unindexed program or a pool you did not expect the router to choose. The DexScreener documentation is explicit about which chains and programs the indexer covers, and it is worth checking before assuming a fault.