How to use Dune Analytics? (On-chain data)

Understanding Dune Analytics Interface

1. Dune Analytics operates through a web-based dashboard where users access dashboards, queries, and datasets without installing any software.

2. The homepage displays trending dashboards, recently updated visualizations, and community contributions sorted by blockchain network.

3. Navigation relies on the top bar: Explore, Dashboards, Queries, Datasets, and Create — each offering distinct entry points into on-chain data exploration.

4. Every dashboard includes interactive charts, filters, and raw data tables that respond in real time to parameter adjustments like date ranges or address inputs.

5. Users can fork any public dashboard or query to customize metrics, modify SQL logic, or adjust visual encodings without affecting the original version.

Writing and Executing SQL Queries

1. Dune supports standard PostgreSQL syntax with extensions for blockchain-specific functions such as ethereum.blocks, ethereum.transactions, and erc20.token_transfers.

2. Queries execute against pre-indexed tables synced from Ethereum, Polygon, Arbitrum, Optimism, Base, and other EVM-compatible chains.

3. A single query may join multiple tables — for example, linking transaction hashes from ethereum.transactions to transfer events in erc20.token_transfers using common keys like block_number and tx_hash.

4. Parameterized queries accept user-defined inputs like wallet addresses or token contracts, enabling dynamic analysis across different entities without rewriting code.

5. Query results render as tables, line charts, bar graphs, or pie charts depending on visualization settings selected before execution.

Building Custom Dashboards

1. Dashboards consist of one or more panels, each powered by an individual SQL query or embedded external chart.

2. Panel configuration allows toggling between chart types, setting axis labels, defining aggregation windows, and applying conditional formatting rules.

3. Filters applied at the dashboard level propagate across all panels, letting users isolate data by chain, date range, contract address, or protocol category.

4. Dashboard permissions support public sharing, team collaboration via workspaces, or private viewing restricted to specific accounts.

5. Version history tracks edits, enabling rollback to prior states and comparison of metric definitions over time.

Interpreting On-Chain Metrics

1. Active addresses represent unique wallets interacting with a contract or network within a defined period — not necessarily human users but cryptographic identities initiating transactions.

2. Transaction volume excludes failed calls and internal transfers, counting only successfully executed operations recorded on-chain with gas fees paid.

3. Token inflows and outflows track net movement across bridges, centralized exchanges, and DeFi protocols using balance delta calculations across time intervals.

4. Gas usage trends reflect network congestion levels, smart contract complexity, and adoption patterns of new opcodes or precompiles introduced in upgrades.

5. Whale activity is identified by filtering transfers exceeding predefined thresholds — often set relative to total supply or median transfer size per token.

Frequently Asked Questions

Q: Can I query non-EVM chains like Solana or Bitcoin on Dune?A: No. Dune currently indexes only EVM-compatible blockchains including Ethereum, Polygon, Arbitrum, Optimism, Base, Gnosis, and Avalanche C-Chain.

Q: Do I need coding experience to use Dune Analytics?A: Basic usage requires no SQL knowledge — many dashboards offer filter controls and prebuilt visualizations. However, custom analysis demands familiarity with SQL syntax and blockchain data schemas.

Q: Are Dune queries real-time?A: Data syncs with a slight delay — typically under five minutes for Ethereum mainnet and under two minutes for most L2s. Finality confirmation introduces minor latency before inclusion in indexed tables.

Q: Can I export raw query results?A: Yes. Results can be downloaded in CSV, JSON, or XLSX formats directly from the query result panel after execution completes.