Polymarket dashboards on Dune

What it is

Not a product. A layer.

Dune is a query platform over decoded blockchain data: you write SQL, you get a table, you pin the result into a dashboard, and the dashboard has a public URL. Because Polymarket settles on Polygon, its entire order flow — fills, conditional-token transfers, positions, resolutions — is on a public chain and therefore queryable. Dozens of people have done exactly that, and the result is a loose body of public Polymarket dashboards: platform volume and open interest over time, unique traders and new wallets per week, CLOB activity broken down by market, per-market holder tables, resolution outcomes and accuracy studies by price bucket. dune.com/rchen8/polymarket, dune.com/lifewillbeokay/polymarket-clob-stats and dune.com/filarm/polymarket-activity are three of the long-standing ones, each on a different author's profile.

This card exists because that layer is genuinely useful and has no other address. It is a single card for a plural thing, and the honest version of the claim is narrow: Dune is the vendor here, and Dune publishes the platform, not the dashboards. Each dashboard belongs to the person who wrote it, carries no support commitment from anyone, and can be changed or deleted by its author without notice.

What the layer offers that no hosted dashboard does is the query. Every chart on a public dashboard can be opened, read as SQL and forked into your own copy. When a number looks wrong, you can find out what it was actually measuring instead of emailing support.

Availability

Open to anyone with a browser. Reading and copying a public dashboard needs no account at all on the free plan, there is no KYC, and Dune sets no geographic restriction that affects reading. Since nothing here touches a venue, nothing here can be geoblocked on a venue's behalf — a reader who cannot use Polymarket can still read every chart about it.

An account is needed to run or schedule your own queries, and a paid plan for private work, CSV exports and higher API limits.

Checked on 19 September 2026.

Pricing

Free is view-only access to all of Dune: view and copy any dashboard or query, explore all data collections, community support, one seat. That is the whole of what a reader of other people's Polymarket dashboards needs.

Paid plans buy the ability to run your own work, and they are metered in credits — executing queries, exporting data and programmatic access all draw on a monthly allowance, with AI actions charged at 10 credits each. On 19 September 2026 the plan table listed Analyst at 4,000 credits a month with 3 seats, Plus at 25,000 credits with 10 seats, private queries and dashboards and CSV data exports, and a custom Enterprise tier. The displayed prices are not recorded as tiers on this card for one specific reason: the page loads with the yearly toggle pre-selected, and it advertises 15% off for yearly, so the two figures it shows in large type are annual-billing rates rather than the month-to-month rate this catalogue stores. Read them off the monthly toggle before you budget.

One line matters more than the price for anyone thinking about redistribution: on Free, Analyst and Plus the data licence is internal use only. A commercial licence is an Enterprise conversation.

Markets & resolution

Nothing here resolves anything, and nothing here trades. Every figure is derived from Polymarket's on-chain record, so resolution is whatever Polymarket's own process — the UMA optimistic oracle — decided, visible after the fact as a settlement on chain.

Coverage is therefore the whole of Polymarket: politics, sports, crypto, company events and the rest, with no editorial selection, because the source is the chain rather than a venue's feature list. It also means the data is post-trade rather than live. A Dune query reads blocks that have already been indexed, so it is the right tool for what happened and the wrong tool for what the book looks like right now.

Integrations

SQL is the interface, and it is the point. Beyond the browser there is a REST API metered from the same credit allowance, with plan-level rate limits (the plan table lists 40 calls a minute on Analyst and 200 on Plus), CSV export on the paid tiers, and an official Python client — the dune-client package, Apache-2.0, source at github.com/duneanalytics/dune-client, version 1.12.0 published on 10 September 2026. Alerts are available with a small per-plan allowance.

There is no WebSocket. There is an official MCP server, published under Dune Agents at dune.com/agents and documented alongside a CLI: it authenticates with your Dune account over OAuth and exposes table discovery, search by contract address, saved queries, query execution, results and credit usage, so it draws on the same credit allowance as everything else. An agent-payment route billed per request over HTTP 402 is documented beside it.

Limitations

A dashboard breaks with the schema it stands on, and nobody tells you. A query is written against decoded tables for particular contracts. Redeploy a contract, change a proxy, rename a decoded table, and the chart either errors, silently drops rows, or keeps drawing a line that no longer means what it meant. The author may notice. They have not promised to.

There is no definition to agree on. One author's "volume" counts notional at fill, another's counts conditional-token transfers, a third excludes the venue's own liquidity operations. Comparing two Polymarket dashboards is comparing two opinions about a definition, and the only way to settle it is to read both queries.

Freshness is the indexer's, not the market's. These are batch-indexed on-chain reads, minutes to hours behind, sometimes more after a chain reorganisation or a pipeline incident. Nothing here is a live tape.

Off-chain venues are invisible, with one gated exception. Dune sees chains. A venue that keeps its book in a database is not in the chain data at all, which puts a hard ceiling on cross-venue work. Kalshi is the exception: Dune loads it as partner data from Kalshi's public reporting, refreshed about hourly, and its three current tables - market details, market trades and hourly candles - are each marked Gated in Dune's documentation. Two legacy daily-aggregated report tables sit beside them.

Abandonment is the normal end state. Scheduled queries and scheduled dashboards expire after three months on the Analyst plan - the free plan cannot schedule at all - and a public dashboard whose author moved on keeps its URL, its title and its last successful result. A stale chart looks exactly like a fresh one.

Internal use only on every plan below Enterprise, so a chart you found here is not something you can republish into your own product.

Alternatives

Polymarket Analytics and Predicts.guru are hosted, live and need no SQL, at the cost of you not being able to see how any number was computed. Polyrama adds Kalshi, which on Dune sits in gated partner tables rather than in chain data.

Goldsky's Polymarket datasets put the same on-chain fills and positions in a database you run, backfilled and then streamed, which is the step past forking a query.