Dune

Dune is an on-chain data platform. It turns blockchain data into queryable tables and dashboards, so analysts and curious users can explore activity across protocols, wallets, markets, and chains.

How Beginners Can Use It

You do not need to write SQL on day one. Start by searching for a project name and opening public dashboards. Look for dashboards with clear descriptions, recent updates, and understandable charts.

What It Solves

Crypto projects often make growth claims. Dune helps people inspect public data instead of relying only on screenshots or announcements. Researchers can build dashboards; readers can compare trends over time.

What to Watch Out For

A dashboard is only as good as its query. Check the author, update time, filters, and assumptions. Different dashboards may answer similar questions in different ways.

Start With Dashboards, Not Queries

Most of what a newcomer wants from Dune already exists as a public dashboard someone else built and maintains. Searching for a protocol or a topic and reading existing work is the fastest route to an answer, and it requires no SQL at all. It also shows you how experienced analysts frame a question, which is more useful than learning syntax in isolation. Every chart on a public dashboard exposes the query behind it, so a dashboard doubles as a worked example you can read and adapt.

Where the Data Comes From

Dune indexes raw blockchain data — transactions, logs, traces — and organises it into queryable tables, with decoded tables for contracts whose ABIs have been submitted. This matters for two reasons. Everything you can query is public on-chain data, so nothing here reveals anything a block explorer could not, and the analysis is only as good as the addresses it filters on. If a contract has not been decoded, its activity may be missing from the convenient tables even though the raw events are present.

Writing a First Query

A useful first query is usually a count or a sum grouped by day, filtered to one contract address. Fork an existing query that already targets the protocol you care about, change the address or the date range, and run it — this teaches the table structure much faster than starting from a blank editor. The most common early frustration is a query that runs for a long time and returns nothing, which almost always means the address is wrong, the case does not match, or the data lives in a different table than expected.

The Misreadings That Happen Most

Wallet counts are not user counts; one person can hold many addresses and frequently does. Transaction volume includes wash trading, bot activity and internal transfers unless explicitly filtered out. A sharp change in a chart is often a change in how the protocol works, or in how the query's contracts were deployed, rather than a change in behaviour. Before drawing a conclusion from someone else's dashboard, it is worth opening the query and reading what it actually counts — the gap between the chart title and the filter logic is where most bad takes originate.

Official Links

• Dune: https://dune.com/
• Documentation: https://docs.dune.com/
• API docs: https://docs.dune.com/api-reference/overview/introduction