On-chain Analytics Platforms

What this category is

Products that read the chains themselves rather than the venues on top of them. The raw material is public and free; what is sold is indexing, labelling and the judgement embedded in a metric's definition.

The boundary against market data runs through where the number comes from, not what it describes. A token's price on a DEX is market data even though the trade settled on-chain. A token's holder distribution is on-chain analytics even though it moves the price. Products that do both are listed under the job they are bought for, with the other as a secondary category — which is why the listing below carries five market-data APIs alongside the nineteen cards that call this category home.

Protocol revenue, token unlocks, ETF flows and asset research used to be filed here too. Since 8 October 2026 they have a category of their own, fundamentals and research, because the reader modelling a protocol's income statement or a token's unlock schedule never shortlists against an exchange netflow chart or a label set, and the reader of those never needs an income statement. If your question is what a protocol earns or when supply is released, start there.

Three products, one category

Comparing across these three is close to meaningless; comparing within one is exactly what a buyer needs. The job facet on each card says which one it is.

A SQL editor over indexed chain data — Dune, Allium, Footprint Analytics and Bitquery. You write the query. The product is the indexing, the schema and the execution engine, and the ceiling is your own SQL. Buy this when the question you have is not one somebody else has already asked, and expect to spend time on the schema before you get an answer. Note that only three of those four actually speak SQL — Bitquery is GraphQL, which is a different skill and a different query you cannot lift from a colleague's dashboard. The Etherscan API and, for Solana, the Solscan Pro API are filed under the same job and sit at the far end of it: no query language at all, one address, token or contract per call. That is the right tool when the question is what happened at one address, and the wrong one the moment it spans thousands.

A labelled view of the chain — Nansen, Arkham, Bubblemaps, Cielo and Whale Alert as dashboards, and MadeOnSol Data API as the same kind of label set, narrowed to Solana launchpad trading and delivered to code. Wallet Master labels Solana wallets by what a copier would have earned from them rather than by who owns them. The product is the label set: the work of deciding that this address is a particular exchange's hot wallet and that one is a fund. You do not write queries; you read somebody's attribution. Buy this when the question is "who", and understand that you are buying a judgement you cannot audit. Labels are proprietary, rarely dated, and wrong often enough to matter. Following a named address is a feature that reaches well beyond these seven, and the wallet-tracking collection sorts every card that carries it.

A curated metric set — Glassnode, CryptoQuant, Santiment and its API sibling SanAPI, with two narrower ones: HyperTracker, every Hyperliquid wallet sorted into size and profit cohorts, and Look Into Bitcoin, Bitcoin alone. Somebody has already defined the metrics they think are worth watching, exchange netflow and holder behaviour among them, and computes them consistently. You get comparability over time and no ability to ask anything outside the list. Buy this when you want the same number next quarter that you got this quarter.

Nothing here is as fresh as it looks

Nine of the nineteen cards record a latency that is not real-time: Dune, Allium, Footprint Analytics, Bubblemaps, Glassnode, CryptoQuant, HyperTracker, Look Into Bitcoin and Wallet Master, which recomputes its metrics hourly, sit at "delayed". Ten claim real time — Arkham, Nansen, Cielo, Whale Alert, the MadeOnSol Data API, Bitquery, the Etherscan API, the Solscan Pro API, Santiment and SanAPI.

A real-time claim is also a claim about a tier. Santiment's free dashboard runs thirty days behind, and the cheapest of its plans whose API access carries no time lag is the 249-dollar Max. The MadeOnSol Data API's free key reads its live feeds five minutes behind; the lag goes at Pro.

This is not a flaw and it is rarely disclosed as a lag. Indexing a block, decoding contract calls, resolving labels and recomputing a metric are four sequential steps, and a platform that recomputes a daily series has no reason to do it more than daily. What it means for you is narrow and absolute: a decision that has to be made inside a block cannot be made from this category. Front-running a whale is not a product here. Understanding what a whale did is.

The dashboard and the API are two products at two prices

The catalogue has a natural experiment sitting in it. Santiment ships two cards because it is two products — the dashboard and SanAPI, the programmatic access to the same numbers — and the cheapest paid month on the API card is more than three times the cheapest paid month on the dashboard. That is the shape across this whole category, usually hidden inside one pricing page rather than split across two.

If you intend to pull numbers into your own system, price the API tier, not the one on the front page. The gap between the two is routinely larger than the gap between free and paid.

The pricing that is not published follows the three kinds above rather than the vendors. Every one of the query platforms keeps a tier with no number on it, and Allium publishes no number anywhere. The labelled products mostly do not — Nansen prints a per-call rate next to its monthly plans, Arkham prices its intel API by the month, Cielo and Whale Alert print every plan, Wallet Master prints both of its plans and keeps only a commercial-use Custom tier unpriced, Bubblemaps charges nothing for the map at all, and the MadeOnSol Data API's one unpriced plan is an Enterprise contract its page starts at 1,000 euros a month. What Bubblemaps does instead is reserve its advanced features for holders of the vendor's own token, with no threshold published, which is a cost that never shows up in a price comparison because it is not a price; a token threshold is not a price is the long version. The per-category counts are on tools you cannot buy without a sales call, and why the silence clusters where it does is in why this market won't quote you a price.

The mistake this category invites

Two platforms' versions of the same metric can differ by more than the thing you are measuring. "Active addresses" can mean senders, receivers, or either. Exchange netflow depends entirely on whose label set says which addresses belong to the exchange, and those label sets are built by different teams from different evidence.

None of that is error. It is two methods, and the numbers are not interchangeable even when they carry the same name — the same problem the price side of the catalogue has with aggregate prices, one layer down. The practical rule is to pick one platform per series and stay on it, because a chart that switches sources mid-way is an artefact with a trend drawn through it. Glassnode versus CryptoQuant is the two-vendor version of this argument in full.

What to check before you commit

Which chains, at what depth. Every platform here claims multi-chain. Depth varies enormously: a chain may be indexed to full contract-call level, or it may be balances and transfers only. The chain you care about is either a first-class citizen or a line in a coverage table, and the table does not distinguish.

Entity labels go stale silently. An address labelled as an exchange wallet two years ago is still labelled that way after the exchange stopped using it. Ask when the label set was last revised, and treat an unlabelled address as unlabelled rather than as retail.

Historical recomputation. When a platform revises a metric's definition, some backfill the history and some do not. If you are charting a two-year series, that decision is the difference between a trend and an artefact.

What the credit actually buys on a query platform. A metered plan on a SQL product is charged against execution, not against calls, so an unselective query costs what a careless index costs. The meter, the window and the penalty are three separate rate-limit choices, and they are made independently.

Whether the output may leave your organisation. A research subscription and a redistribution licence are different purchases here exactly as they are for price data, and the clause is in the terms rather than on the pricing page.

What is not here

Block explorers, node providers and indexing infrastructure sold as a developer backend. Reading a single transaction is not analysis, and an RPC endpoint is plumbing rather than a market tool. The Etherscan API is not an exception to that: the explorer itself is not listed, and its paid API is, because that is bought by people building on chain state. Wallet and custody products are out of scope for the catalogue entirely. Anything whose output is which token to buy is advice, not tooling.

One more thing belongs in this section, because it is a fact about the category rather than about any card in it. Three on-chain platforms have pages here written for readers whose product has already gone, and all three shut down outright rather than changing their terms: Flipside, IntoTheBlock and Parsec. Read that as a warning about dependency rather than about any vendor on this page: a dashboard is a habit, but a query you scheduled, a metric you charted for two years and a label set you cited are all things that stop existing on somebody else's timetable.