{"slug":"explorer-chain-coverage","title":"Block explorer chain coverage, registered vs fresh-indexed","subtitle":"Chains where each block explorer family serves a working indexer, probed daily against the vendor's own machine-readable registry, with a separate view over the 50 most active mainnets.","category":"Explorers","metric":"Chain coverage","unit":"count","status":"live","higherIsBetter":true,"value":195,"leader":{"name":"Blockscout","slug":"blockscout","value":195},"rankings":[{"name":"Blockscout","slug":"blockscout","ms":{"p50":195,"p90":459,"p99":18,"mean":195},"successRate":100,"sampleSize":195},{"name":"Routescan","slug":"routescan","ms":{"p50":32,"p90":36,"p99":6,"mean":32},"successRate":100,"sampleSize":32},{"name":"Etherscan","slug":"etherscan","ms":{"p50":30,"p90":34,"p99":17,"mean":30},"successRate":100,"sampleSize":30},{"name":"Blockchair","slug":"blockchair","ms":{"p50":11,"p90":14,"p99":5,"mean":11},"successRate":100,"sampleSize":11}],"sparkline":[194,194,194,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195,195],"sampleSize":268,"asOf":"2026-07-08T13:35:13.092Z","headline":"Blockscout leads chain coverage at 195 (24h) on Block explorer chain coverage, registered vs fresh-indexed.","quote":"Blockscout leads chain coverage at 195 (24h) on Block explorer chain coverage, registered vs fresh-indexed. Source: OpenChainBench (https://openchainbench.com/benchmarks/explorer-chain-coverage).","cite":{"plain":"OpenChainBench. \"Block explorer chain coverage, registered vs fresh-indexed\". Retrieved 2026-07-08. https://openchainbench.com/benchmarks/explorer-chain-coverage","bibtex":"@misc{ocb_explorer_chain_coverage,\n  author = {OpenChainBench},\n  title  = {Block explorer chain coverage, registered vs fresh-indexed},\n  year   = {2026},\n  url    = {https://openchainbench.com/benchmarks/explorer-chain-coverage},\n  note   = {Retrieved 2026-07-08}\n}","apa":"OpenChainBench. (2026). Block explorer chain coverage, registered vs fresh-indexed. Retrieved July 8, 2026, from https://openchainbench.com/benchmarks/explorer-chain-coverage"},"pageUrl":"https://openchainbench.com/benchmarks/explorer-chain-coverage","ogImage":"https://openchainbench.com/api/og/explorer-chain-coverage","source":"https://github.com/ChainBench/OpenChainBench/tree/main/harnesses/explorer-chain-coverage","methodology":["registered = mainnet chains the vendor self-declares via a machine-readable surface: Blockscout's Chainscout registry, Etherscan's keyless chainlist, Routescan's blockchains endpoint, Blockchair's aggregate stats. Testnets are excluded everywhere; for Etherscan the mainnet set is a pinned chain-id allowlist rather than a name heuristic, and any new unclassified listing is excluded and logged until reviewed, so a devnet can never silently inflate the count.","verified = registered chains whose latest indexed block is younger than 60 minutes at probe time, read from each family's own API (Blockscout /api/v2/blocks, Routescan blocks, Etherscan getblocknobytime against its index, Blockchair best_block_time). A 200 from a stalled indexer does not count. Quiet chains get a second chance: a block older than 60 minutes still passes when its age is under 10x the chain's own average block time, so on-demand rollups are not punished for being idle.","A freshness ladder is measured from the same probes: verified (60 minutes) and verified_strict (5 minutes). Families converge at the loose rung and diverge at the tight one, which separates real-time indexers from batch pipelines at zero extra probing cost.","Vantage and denominators, disclosed: probes run from one EU vantage once per day, so a single transient network fault can cost a chain one cycle (publish-then-leave limits the blast radius). The top-50 list contains 17 non-EVM chains that EVM-only families structurally cannot serve; their per-family ceilings are roughly 33 of 50 for Blockscout, Etherscan and Routescan, and the raw counts should be read against those ceilings.","top-50 = of the 50 most economically active mainnets (pinned quarterly from a DefiLlama TVL + fees blend, list in the harness source), how many pass the same freshness gate on this family. Raw chain counts reward hosting ghost rollups; this column answers what integrators actually ask and is the one where breadth leaders can lose.","Operator attribution: many Blockscout instances are run by the chain teams themselves, not by Blockscout. The registry's hostedBy field is preserved in the harness so the distinction stays auditable; the count measures the software family's working footprint, which is the claim its marketing makes.","Cadence: one probe cycle per day, ~600 spaced upstream calls, every surface free. Blockscout's sweep talks to hundreds of distinct hosts through a small worker pool; single-host families are spaced 600ms. Quota-truncated cycles publish nothing. Every family is probed keyless except Etherscan's freshness calls, which use a free key; its registered count stays keyless.","Source: https://github.com/ChainBench/OpenChainBench/tree/main/harnesses/explorer-chain-coverage"],"license":"CC-BY-4.0"}