While all the core functionality you expect from Dune is available in Dune v2 the new version of Dune brings changes to how queries and refreshing work, both on the surface and under the hood.
By default, new queries are not saved to your queries so you can play around and test various ideas quickly. If you want to keep your work, remember to hit the Save button and give your query a name.
This means that if you navigate away from a page without saving, your work is lost. If you allow notifications from dune.xyz in your browser, the app will notify you when you navigate away from unsaved content.
The same applies to forks. A fork is not saved to your queries before you click the Save button and give your fork a name.
We’ve merged the old save and execute buttons into a single button, Run. When you click Run on a saved query, any changes you’ve made to the query text is saved and the query is queued for execution.
Useful tip: Press CMD / CTRL + Enter to run your query.
Running query snippets
If you mark parts of your query, the button changes to Run selection, and executes the part of the query that you’ve marked. This will updates the results and visualizations in the process but not save the query.
Useful tip: if you want to execute the whole query without saving it, select all of the query (CMD / CTRL + A) and then hit Run selection.
There’s also changes to how results are refreshed. Over the last months we’ve been redesigning our entire query execution backend to bring large improvements to how Dune works.
When a visualization is viewed, either on a query page or on a dashboard, the Dune backend will inspect the age of the most recent result. If the result is stale (currently defined as >3 hours old), Dune will automatically queue an execution for this query and run it in the background.
This means that your dashboards will always be kept up to date when they are being viewed.
Query creators does not need to set a refresh scheduele and the scheduling feature has been deprecated as it is no longer needed to keep results fresh.
We’re also bringing changes to how queueing works in Dune. When you manually click Run on a query an execution is queued. Every user on Dune can queue 3 queries at the same time (pro users have more, see our pricing page for more info).
Automatically refreshed results (as we talked about above) does not use the query creators queuing credits nor the viewing user’s.
A faster and better looking Dune - the whole Dune app including all the charts have gotten a big facelift. The app is now also many times faster.
Query parameters - what is probably Dune’s most underrated feature has gotten a major upgrade. It’s now super easy to filter any query or dashboard for a token, address or anything really. Meaning you can turn your queries and dashboards into interactive apps for onchain data.
See all content without having to log in - simply copy and share the link from the page you are on. The exception is for paid users that make their content private, more details on our pricing page.
Errors show on the relevant line - when running your queries you will see error messages directly on the relevant line in your code.
Click query title to go to query from a dashboard
We’d love to get your feedback on your experience with Dune v2 in the #feedback channel in our Discord. You can also contact [email protected] if you face any issues.
PS. There are a few visualisation types that are currently not supported in Dune v2: pivot, cohort, funnel, heatmap and bubble. We’ve emailed the users that are affected. If you have not been emailed all your queries and visualisations should work seamlessly in v2.