36 chains
33M+ tokens
36M+ pools
234 DEXes
Networks
Every chain DexPaprika covers, ordered by 24 hour trading volume. Thenetwork column is the
value the API expects wherever an endpoint takes a network.
What these numbers mean
The two pool figures count different things, and both are accurate. 36M+ pools and 33M+ tokens are total database coverage: everything DexPaprika has recorded across all 36 chains. Actively traded pools in the table above counts pools with recent trading activity, which is the set pool search returns. It is a much smaller and faster moving number, because most pools ever created stop trading. Indexing is not instantaneous, so a brand new pool reaches the database before it appears in the active set. Which one you want depends on the question. For “how much of the DEX market does this cover”, use the totals. For “how many pools can I query on Base right now”, use the table. The DEX columns differ for a similar reason. 234 DEXes counts every DEX recognised across all chains, while the table lists the 199 currently returned by the per-chain DEXes endpoint.Check a specific asset
The numbers above answer “how much does DexPaprika cover”. To answer “do you have this particular token or pool”, use the coverage checker, which searches the live dataset by contract address, name or symbol.Get these figures yourself
Both sources are public and need no API key./stats is also a reasonable liveness check; it is cheap and reflects the latest successful
aggregation.