Users with SQL knowledge can build custom analysis with DuneSQL, while those without technical experience can explore public dashboards and queries created by the Dune community. This article explains how Dune works, what data it covers across more than 100 blockchain networks, how queries, charts, and dashboards are used, what its pricing plans look like, which public dashboards are worth reviewing, and how to use the platform more effectively.
For anyone making decisions around tokens, DeFi, NFTs, or broader blockchain ecosystems, Dune is relevant because it makes on-chain research more accessible, transparent, and reproducible. It can help users understand historical and recent activity, but its data should not be treated as a guaranteed market forecast: dashboard results depend on the underlying query, selected contracts, filters, data coverage, and refresh status.
Dune Analytics is a blockchain data platform that converts raw on-chain information into queryable datasets. Users can write SQL queries to analyze blockchain transactions and smart contract activity, then turn the results into charts, tables, counters, and dashboards.
The platform supports multiple types of data. Raw blockchain tables contain information such as blocks, transactions, logs, and traces. Decoded tables translate smart contract events and function calls into more readable formats, while curated datasets standardize commonly used information such as decentralized exchange trades, token transfers, prices, stablecoin activity, and cross-chain bridge data.
Dune can be used to research metrics such as:
Daily and monthly active addresses;
Token transfer volume and holder distribution;
Decentralized exchange trading volume;
Protocol fees and revenue;
DeFi deposits, withdrawals, and liquidity;
NFT sales, traders, and collection activity;
Stablecoin supply and transaction flows;
Blockchain usage, gas consumption, and contract interactions.
Many public dashboards and queries can be viewed without creating an account. An account is generally required to save queries, create visualizations and dashboards, organize work in a library, and use additional workspace features.
Dune is community-driven because users can publish queries and dashboards for others to inspect, copy, and improve. However, this does not mean that every dashboard is an official or independently verified source. Users should review the query logic, data tables, filters, and update time before relying on a result.
Dune indexes data from supported blockchain networks and organizes it into SQL-accessible tables. Users can query those tables through the Dune Data Hub, visualize the results, and combine multiple visualizations into a dashboard.
Dune historically referred to active community analysts as “wizards.” Today, the platform is used by a wider range of participants, including independent analysts, protocol teams, developers, data engineers, investment researchers, and organizations.
Users can work with Dune in two main ways. The first is to explore existing dashboards and queries created by other analysts. The second is to write a custom DuneSQL query for a specific contract, protocol, token, wallet, or blockchain metric.
Here is an overview of how Dune Analytics works.
Dune collects and indexes blockchain data from a wide range of supported networks rather than focusing primarily on Ethereum. Its current data products cover more than 100 chains and include raw data, decoded contracts, curated cross-chain datasets, partner-contributed data, user-uploaded information, and options to directly share data into external warehouses such as Snowflake and BigQuery.
Raw data includes the original records generated by a blockchain, such as transactions, logs, blocks, and traces. This information is comprehensive but may require more technical knowledge to interpret.
Decoded data makes smart contract activity easier to analyze. Dune uses a contract’s application binary interface, or ABI, to translate machine-readable event logs and function calls into structured SQL tables.
Curated datasets provide standardized tables for frequently studied categories. These can simplify cross-chain research because analysts do not need to normalize every protocol, token, or blockchain manually.
Dune data is updated through its indexing and processing pipelines, but it should not always be described as fully real-time. Data freshness can vary by blockchain, table, query schedule, indexing status, and dashboard refresh settings.
Users can write SQL queries to retrieve specific blockchain data. Dune uses DuneSQL, a query engine based on TrinoSQL and adapted for blockchain analytics.
A query may calculate the number of daily users interacting with a protocol, track token transfers between selected wallets, compare decentralized exchange volumes, or measure fees generated by a smart contract.
For example, an analyst researching a DeFi protocol could query deposits, withdrawals, swaps, unique users, and transaction volume over time. The results would first appear as a table, with each column representing a selected metric.
Dune also supports query parameters. Parameters allow dashboard viewers to change values such as a blockchain, token address, wallet, or date range without editing the underlying SQL.
Once a query has returned results, users can create visualizations such as line charts, bar charts, area charts, tables, counters, and other formats. Each visualization can be configured according to the structure of the query output.
Visualizations can then be added to a dashboard as widgets. A dashboard may combine several queries to present a broader view of a network, protocol, token, or market category.
Dune dashboards can also include text, images, explanations, methodology notes, and links. This helps analysts provide context rather than presenting isolated numbers without explaining how they were calculated.
In summary, Dune transforms indexed blockchain data into SQL tables. Users query those tables, convert the results into visualizations, and organize those visualizations into dashboards that can be shared with others.
Users can begin with Dune by exploring existing dashboards or by creating an account and writing a custom query. New users do not need to start with advanced SQL. Browsing public dashboards and inspecting the queries behind them is often the easiest way to understand the platform.

Source: dune.com
To create a Dune account, open the platform’s sign-up page and follow the current registration instructions. The required fields and authentication options may change as Dune updates its account system.
After signing in, users can save queries, create dashboards, manage content through their library, and access the features included in their account plan.
Creating an account does not require connecting a crypto wallet. Dune is primarily a data platform, so users should be cautious of external pages or messages that unexpectedly request private keys or seed phrases.
Dune’s interface provides access to public content, the query editor, the data catalog, personal or team libraries, and account settings. Button names and menu positions may change as the platform is updated, but the core workflow remains the same: discover existing analysis, inspect the underlying data, create queries, and build dashboards.
After signing in, users can browse public dashboards through Dune’s search and discovery features. Dune allows users to search across dashboards, queries, analysts, and teams, and apply filters to narrow the results. A lot of articles and researchers use Dune dashboards as sources, and the platform has processed over 6.5 million queries.

Source: dune.com
Users can search for a blockchain, protocol, token, or data category. For example, searching for “Solana” may return dashboards covering network activity, decentralized exchanges, stablecoins, NFTs, wallets, or specific applications.

Source: dune.com
Before relying on a dashboard, users should check:
The dashboard creator;
The last refresh or execution time;
The methodology and description;
The blockchain networks included;
The relevant contract addresses;
The date range and filters;
The underlying SQL queries.
Opening a dashboard displays its visualizations and supporting text. Some dashboards also include interactive parameters that allow viewers to change dates, networks, tokens, or other inputs.

Source: dune.com
A Solana dashboard might show daily active addresses, transaction activity, DEX volume, protocol usage, or user interactions. These metrics can help describe on-chain behavior, but they do not automatically indicate whether an asset’s price will rise or fall.
Different dashboards may report different values for apparently similar metrics. For example, “active users” may refer to unique sending wallets, unique signers, protocol interactions, or another definition. Users should inspect the query methodology before comparing results.
Users can also search for public queries. A query contains the SQL logic used to generate a dataset or visualization, allowing users to examine how a metric was calculated.

Source: dune.com
If a useful public query already exists, users can inspect its source code and fork it. Forking creates an editable copy, making it possible to change filters, contract addresses, date ranges, or other conditions without altering the original query.
If an appropriate query cannot be found, users can create a new one through the current Create or Query Editor interface.

Source: dune.com
The Query Editor includes a Data Explorer that allows users to search raw blockchain tables, decoded contracts, curated datasets, partner data, and uploaded datasets. Users can inspect table schemas and insert table or column names into the editor.

To create a Solana analysis, for example, users can search the Data Explorer for Solana tables and select the dataset that matches the intended metric. Available tables and their names may differ from those shown in older interface screenshots, so users should use the current catalog rather than relying only on a past menu path.

Source: dune.com
After selecting a table, users should review its columns and documentation before writing the query. A table may contain timestamps, transaction identifiers, wallet addresses, instructions, token amounts, or other fields.

Source: dune.com
A basic query workflow is:
Identify the metric or question;
Find the appropriate table;
Review the schema and data types;
Write the DuneSQL query;
Add date, blockchain, or contract filters;
Run the query;
Check the output for errors or unexpected results;
Save the query with a clear name and description.
The current Dune Query Editor provides features such as syntax highlighting, autocomplete, inline error messages, results sorting, version history, parameters, query scheduling, CSV export, and query lineage. Availability may depend on the user’s plan.
After running the query, users can save it and create a visualization from the result.

Source: dune.com
Saved queries and dashboards can be found in the user’s library or workspace.

Source: dune.com
Users who are not yet comfortable with SQL can begin by forking a public query and changing only one element, such as the date range or token address. This is generally easier than building an advanced query from an empty editor.
Dune offers a free plan and multiple paid options for individual analysts, teams, and enterprises. Its current model uses credits, with query and data usage consuming credits according to the resources required.
The available plans, prices, included credits, privacy options, export limits, API capabilities, and team features may change. Users should therefore check Dune’s current pricing page before selecting a subscription rather than relying on fixed prices shown in an older screenshot.
Free accounts can still be used to explore public dashboards, create queries, and learn DuneSQL. Paid plans may provide additional credits, private content, team collaboration, faster or larger workloads, automated refreshes, API access, exports, and other advanced functions, depending on the current offering. Dune’s official credit documentation currently lists Free, Analyst, Plus, and Enterprise options, while the former Premium plan is no longer offered to new subscribers.
Source: dune.com
Because the image may show an earlier pricing structure, it should be treated as a visual example rather than the definitive current plan list. The live Dune pricing page should remain the source of truth.
Dune combines blockchain data access, SQL analysis, visualization tools, and community-created research in one platform. This can reduce the infrastructure required to perform on-chain analysis independently.
Dune makes a large amount of blockchain data and public analysis available through a browser. Users without SQL knowledge can browse public dashboards, while analysts can inspect and fork many publicly available queries.
The platform should not be broadly described as fully open-source. Its collaborative value comes from publicly shared queries, dashboards, data models, and community contributions, while the complete Dune platform is not simply an open-source software project.
Public queries improve transparency because users can inspect the SQL behind many dashboard metrics. However, accessibility does not guarantee accuracy. Community dashboards can contain outdated contract addresses, incomplete filters, duplicated data, or methodological errors.
Dune continually indexes blockchain data and allows queries and dashboards to be refreshed as new records become available. This makes it useful for monitoring recent protocol activity, token transfers, trading volume, stablecoin flows, and network usage.
The phrase “real-time” should be used carefully. Dune data may be close to real time, but delays can occur because of blockchain finality, ingestion, decoding, transformation, query execution, caching, or scheduled refresh intervals.
Users should inspect the dashboard refresh time and understand whether a query uses raw, decoded, or curated data. A recently refreshed dashboard may still rely on a table with a different update schedule.
Dune supports data analysis across more than 100 blockchain networks and provides raw, decoded, and curated datasets. This helps users analyze data across multiple blockchain networks, whether they want to compare activity on different chains or study a protocol operating on several networks.
Its flexible SQL interface supports a wider range of questions than a fixed analytics page. Users can define custom wallet groups, contract lists, token categories, time periods, and calculation methods.
Dune also supports additional workflows through APIs, data exports, uploaded datasets, data warehouse integrations, query scheduling, and alerts. These functions make the platform useful for both one-time research and recurring data operations.
Dune dashboards organize one or more query results into visual reports. They can cover individual protocols, complete blockchain ecosystems, specific wallets, market sectors, or cross-chain trends across Ethereum, Arbitrum, and Polygon.
Users can find dashboards through the global search bar or Discover page. Search results may include dashboards, queries, analysts, and teams, with filters and sorting options available through the current interface, and users can follow the same workflow to explore dashboards for BSC or Optimism.
A useful dashboard should explain what it measures, identify its data sources, provide a clear date range, and allow users to inspect the underlying queries. Dune is a great starting point for finding community-built crypto analytics, but popularity can help identify widely used dashboards only if it does not replace methodological verification.
For example, users researching NFT activity may search for dashboards covering collection sales, marketplace volume, traders, wash-trading filters, floor prices, or wallet behavior.

Source: dune.com
Older dashboards such as Whale Watcher, Smart Money, or marketplace trader dashboards may still provide useful examples, but their current availability and data coverage should be checked directly. NFT marketplaces, contracts, and query tables may change over time.

Source: dune.com
A dashboard showing popular NFT collections may help identify which assets are being purchased by selected wallets or marketplace participants. However, the result depends on how “whale,” “smart money,” or “top trader” is defined.
Users can also search for Bitcoin dashboards.

Source: dune.com
A Bitcoin dashboard may include block production, miner rewards, transaction fees, address activity, inscriptions, token protocols, exchange flows, or other metrics. The available datasets and dashboard content may differ from the older screenshot.

Source: dune.com
Historical miner-reward charts can help explain Bitcoin issuance and fee activity. Users should check whether the visualization uses block subsidies only, total miner revenue, estimated fiat values, or another measurement.
Some dashboards also display query tables containing wallet addresses and balances. These tables may be sortable or downloadable, depending on the dashboard and account permissions.

Source: dune.com
Wallet labels and balance calculations should be interpreted carefully. A single entity may control multiple addresses, while one address may represent an exchange, smart contract, custodian, bridge, or pooled wallet rather than an individual user.
Users can inspect the underlying query to understand how addresses were selected and how balances were calculated. Public queries may also be forked and adapted for further analysis.
Here are several ways to use Dune Analytics more effectively:
Start with a specific question. Define the metric, blockchain, protocol, date range, and contract before writing SQL. A clear question makes it easier to choose the correct dataset.
Begin with public dashboards and simple queries. New users can inspect existing dashboards and fork public queries before creating more complex analyses.
Verify contract addresses. Protocols may deploy multiple contracts, upgrade implementations, or operate across several networks. Missing one contract can materially change the result.
Read the table documentation. Raw, decoded, and curated tables may represent the same activity differently. Check column definitions, data types, chain coverage, and update notes.
Use time filters. Queries without appropriate date filters may scan unnecessary data, run slowly, and consume more credits.
Check for duplication. Joining blockchain tables incorrectly can multiply rows and overstate volume, user counts, or transaction totals.
Define metrics clearly. Terms such as active user, volume, revenue, TVL, and smart money can have multiple definitions. Include the methodology in the query or dashboard description.
Review freshness. Check when a query last ran and whether its underlying data tables are current.
Compare with another source. When a metric is important, compare it with a block explorer, official protocol dashboard, financial report, or another independent dataset.
Use documentation and community resources. Dune provides official documentation, tutorials, and community channels that can help users understand DuneSQL, data models, query performance, and visualization tools.
Dune Analytics is an on-chain data platform that allows users to explore blockchain activity through public dashboards or custom DuneSQL queries. It provides access to raw, decoded, and curated datasets covering more than 100 blockchain networks.
Users can search for existing research, fork public queries, analyze smart contract activity, create visualizations, and assemble dashboards. More advanced users can also work with APIs, exports, scheduled queries, alerts, uploaded datasets, and data engineering tools.
Dune makes blockchain data more accessible, but the platform does not automatically guarantee that every dashboard is accurate. Results depend on the selected tables, contracts, filters, metric definitions, query logic, and refresh status.
For reliable analysis, users should inspect the underlying SQL, verify contract addresses, review data freshness, and compare important metrics with additional sources. Used carefully, Dune can support transparent and reproducible research across DeFi, NFTs, stablecoins, tokens, protocols, and broader blockchain ecosystems.
Yes. Dune offers a free plan that allows users to browse public dashboards, run queries, create visualizations, and learn DuneSQL. Paid plans provide additional credits, private content, collaboration tools, API access, and other advanced features.
No. Users can explore public dashboards and queries without writing SQL. However, creating custom analyses generally requires DuneSQL or adapting an existing public query.
Dune data is often updated close to real time, but delays may occur because of blockchain finality, indexing, decoding, query execution, caching, or dashboard refresh schedules. Users should check the latest refresh time before relying on a metric.
Dune supports data from more than 100 blockchain networks. Coverage varies by chain and may include raw blockchain tables, decoded smart contract data, curated cross-chain datasets, and partner-contributed data.
No. Public dashboards are created by community members and may use outdated contracts, incomplete filters, or different metric definitions. Users should inspect the underlying SQL, methodology, data sources, and refresh status.
A query uses DuneSQL to retrieve and calculate blockchain data. A dashboard combines one or more query results into charts, tables, counters, and explanatory content for easier analysis and sharing. Dashboards are built to be shared with others and can support external analysis apps or reporting workflows.
* The information is not intended to be and does not constitute financial advice or any other recommendation of any sort offered or endorsed by Gate.
* This article may not be reproduced, transmitted or copied without referencing Gate. Contravention is an infringement of Copyright Act and may be subject to legal action.





