Dune — custom on-chain analytics next to the books
For finance teams that want to slice on-chain data their own way. Dune queries surface alongside the Wag3s ledger.
Dune is the SQL-based analytics platform for on-chain data — finance teams use it to build custom dashboards (revenue per chain, treasury composition, MEV exposure). The Wag3s integration is for teams that want to bring Dune query results into the same workspace as the accounting subledger — useful for management reporting that mixes booked-and-classified GL data with raw on-chain analytics.
What the Dune integration does
Dune query result ingest
Saved queries pulled into Wag3s for management reporting.
Reconciliation against subledger
Dune-computed totals reconciled against Wag3s GL postings.
The connection in 4 steps
Add your Dune API key to Wag3s
Generate an API key in Dune Analytics settings. Paste it into the Wag3s data-integrations panel. No special permissions beyond standard API access are required.
Select or configure the Dune queries to import
Choose saved Dune queries by query ID. These are typically treasury-balance, revenue, or on-chain-volume queries your team already maintains. Wag3s pulls the latest result set on a daily schedule.
Dune results surfaced alongside the Wag3s ledger
Query results appear as a management-reporting panel next to your classified GL data. You can compare Dune-computed on-chain revenue against the Wag3s-booked revenue figure for the same period.
Reconciliation report generated
Wag3s produces a reconciliation report comparing Dune-computed totals to GL-posted totals for each configured query. Discrepancies flag for investigation before the period close.
Common configurations
Protocol generates fees on-chain across multiple contracts and chains. The Dune dashboard tracks gross protocol revenue by chain; Wag3s books the classified fee income. The integration lets the finance team reconcile Dune-computed revenue against booked revenue every month-end without manual export.
DAO treasury committee runs Dune queries for treasury composition, token concentration, and runway. The Wag3s integration surfaces these dashboards alongside the accounting subledger so board members see analytics and books in one place without switching tools.
Dune integration questions
Can Wag3s use any public Dune query or only our own?
Both. Wag3s can import results from any Dune query you have API access to — your own private queries or public queries by query ID. We recommend using your own queries for financial reconciliation to ensure the logic is controlled by your team.
How often are Dune query results refreshed?
By default, Wag3s pulls Dune results daily. You can configure a refresh frequency up to every 6 hours depending on your Dune API plan limits. Real-time refresh is not supported due to Dune's execution latency.
Does this replace on-chain data ingestion in Wag3s?
No. Dune is a supplementary data source for management reporting and reconciliation. Core transaction classification and GL posting in Wag3s runs on direct on-chain ingest, not Dune. The two work together — Dune for analytics context, Wag3s for the authoritative audit trail.
Other connectors that pair with this one.
Connect Dune in minutes
Free during Alpha. No credit card. Native sync, audit trail, no spreadsheets.