What is Dune?
Dune is a community-driven blockchain analytics platform. Users write SQL queries against indexed on-chain data to build charts and dashboards, then publish and share them. Much of Dune's value comes from this community: thousands of public dashboards cover protocols, tokens, and NFT collections.
Our measurements
We estimate roughly a 7.6-year track record for Dune. Our latency probe returned about 431 ms, one of the slower responses in this group, which is unsurprising for a query-heavy analytics product. Status transparency is unclear in our data rather than confirmed absent.
- Track record: long-established
- Probe latency: ~431 ms (slower, query-heavy platform)
- Status page: unclear in our data
Strengths and trade-offs
The open, community model is Dune's biggest strength and its biggest caveat. Public dashboards are only as reliable as the person who wrote the query; a popular dashboard can still contain flawed logic or mislabeled data, so read the SQL when it matters. Getting real value usually requires either SQL skills or trust in a dashboard author. Heavier usage and private work sit behind paid tiers.
Why the community model is different
Most analytics products decide what to measure and how, then hand you the result. Dune inverts that: the raw indexed tables are exposed, and the analysis is written in the open by whoever cares to. This transparency is unusual and valuable, because a query's logic can be inspected and forked rather than taken on faith. It also shifts responsibility onto the reader. A polished dashboard with thousands of views carries no guarantee that its author joined the right tables, handled decimals correctly, or filtered out test transactions.
Common pitfalls in Dune dashboards
- Token amounts shown in raw units because decimals were not normalized.
- Double-counting when a query joins tables that both contain the same transfers.
- Stale results when a dashboard's query has not been refreshed against recent blocks.
- Chain or contract-address filters that quietly miss part of the activity.
None of these make Dune unreliable; they make it a tool that rewards scrutiny. The best practice is to open the query behind any number you intend to act on.
Who it's for
Analysts and data-literate users who want to query on-chain data directly or lean on community dashboards, with the judgment to sanity-check what they find. It is less suited to someone who wants a polished, opinionated metric handed to them without context.