DEX indexer with most blockchains, live coverage ranking
DefiLlama leads dex-indexed chains at 479 (24h) on DEX indexer with most blockchains, live coverage ranking. Number of blockchains where each major DEX indexer actively indexes pools + swap volumes, audited every six hours against each provider's public networks endpoint.
TL;DR. As of , DefiLlama leads dex-indexed chains at 479 (24h) on DEX indexer with most blockchains, live coverage ranking. Source: OpenChainBench, https://openchainbench.com/benchmarks/dex-network-coverage.
This benchmark counts how many blockchains each major DEX indexer officially indexes pools + swap volumes on, audited live every six hours from each provider's public networks endpoint. The number is what a DEX-facing builder actually cares about: given a chain, can this API return pool addresses, live swap events, OHLCV candles and trending pools. Providers on this leaderboard run their own DEX pool indexer as a product (GeckoTerminal `/networks`, Codex `getNetworks`, DefiLlama `/chains`, DexPaprika `/networks`, Sim by Dune `/evm/supported-chains`). Asset-registry coverage (chains where an API knows tokens for contract-address lookup) is a different question measured on the sister bench asset-registry-coverage.
Methodology
We benchmark how many networks each major DEX indexer publishes as actively indexed for pools + swap volumes. The harness fetches the official listing every six hours from five providers (GeckoTerminal, Codex, DefiLlama, DexPaprika, Sim by Dune), deduplicates by chain id or platform slug and counts. Mainnet only. Asset-registry coverage (chains where the provider knows tokens for contract-address lookups) is measured on bench asset-registry-coverage because it answers a different question, an API can list tokens on 300 chains through a market-data pipeline while running DEX pool indexing on only a dozen. Both leaderboards live under Aggregators so a reader can compare a provider on the axis that matches their product.
Frequently asked
Which DEX indexer supports the most blockchains right now?
DefiLlama currently leads at 479 chains across 5 measured providers. The count is read every six hours directly from each provider's own DEX-networks endpoint and deduplicated by chain id, so the leaderboard reflects where each API actively indexes DEX pools + swap volumes today, not a claim from a marketing page.
Why is this bench separate from asset-registry-coverage?
DEX-pool coverage and asset-registry coverage are two different products, not a single metric. GeckoTerminal indexes DEX pools on ~265 chains via `/networks`; CoinPaprika lists 300+ chains in `/v1/contracts` because it indexes token metadata everywhere. Comparing them on one leaderboard makes the number meaningless, a market-data API always wins on chain count while a DEX indexer always wins on pool-level depth. This bench answers the DEX-indexing question. The sister bench asset-registry-coverage answers the token-lookup question.
Does DefiLlama really index DEX pools on 400+ chains?
DefiLlama's `/chains` endpoint tracks every chain with at least one indexed DeFi protocol (DEXes, lending, LSTs, restaking, bridges, oracles), so the count is broader than DEX-only. DEX chains are a subset. DefiLlama sits on the leaderboard because the same crawler backs their DEX-volumes aggregator, and the endpoint is the canonical open reference for `chains with meaningful onchain financial activity`. Read alongside the more DEX-specific counts from GeckoTerminal, Codex and DexPaprika for the DEX-only view.
Why isn't CoinGecko / Mobula / CoinPaprika on this leaderboard?
Those providers are measured on the sister bench asset-registry-coverage because their product is chain-scoped token metadata + market data, not DEX pool indexing. CoinGecko powers GeckoTerminal on the DEX side, but the token-registry number and the DEX-indexed number are measured separately because they answer different questions. Mobula and CoinPaprika are market-data APIs, not DEX pool indexers, DexPaprika is CoinPaprika's dedicated DEX product and is on this leaderboard.
How often is the chain count refreshed?
Every six hours. The harness hits each provider's DEX-networks endpoint, parses the response, deduplicates by chain id, and updates the Prometheus gauge `networks_supported_total{provider}`. Failures leave the previous count in place and increment a `fetch_errors_total` counter, so a temporary outage does not silently drop a provider off the leaderboard.
What counts as a mainnet in this benchmark?
Any chain a provider lists as a production network for DEX indexing, identified by a unique chain id or slug. Ethereum, Solana, Base, Arbitrum, BNB, Avalanche and so on each count once regardless of how the provider labels them internally. Testnet listings are filtered server-side where the provider exposes a testnet flag. Sim by Dune is EVM only by construction of the `/v1/evm/supported-chains` endpoint.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/network-coverage