What this board is
Dune — Fernando Molina Polymarket Markets Data (@fergmolina) is a public Dune dashboard that reads Polymarket's market metadata from an API inside a SQL query and joins it to on-chain trades, so trading volume can be traced back to the individual market — and the individual outcome — it belongs to. It is the dashboard Dune itself uses to demonstrate LiveFetch, the set of SQL functions that make HTTP requests from inside a query.
The author is Fernando Molina, a data engineer who publishes on X as @fergmolina. The board is free to open: no wallet, no exchange account and no paid plan are needed to read it.
The problem it was built to solve
Polymarket settles trades on Polygon, but the questions, outcomes, rules, categories and timestamps that give those trades meaning live off-chain, in Polymarket's Gamma Markets API. A fill therefore arrives as a token ID and a size, with nothing in the on-chain record saying which market it belongs to or which side of the question was bought.
The conventional fix is an external script: call the API, download the market list, build a mapping table of token IDs to markets, then join it to the trades. That approach has two structural weaknesses. The mapping has to be rebuilt and reloaded every time a market is created or resolved, so markets opened after the last refresh stay invisible; and the mapping table becomes an asset someone has to maintain, document and trust.
This board removes the maintenance step. Because the API is called from inside the query, the mapping is generated at execution time — a market created since the last run is picked up by the next one, with nobody editing a lookup table.
What it shows that a venue-wide chart cannot
A single 'Polymarket volume' number answers a question almost nobody is asking. Research, reporting and trading decisions need to know which market moved, and often which answer inside it. Volume, trades and distinct wallets are broken out at three levels — first by Event, then by Market, then by Answer — so a reader can see that a spike came from one outcome rather than from the venue as a whole.
In practice that means the board can answer:
- Which market inside a multi-market event is actually carrying the volume?
- How is activity split across the possible answers to a single question?
- Is participation in a market broad, or concentrated in a small set of wallets?
- How does activity compare across events in the same category?
Transparency about its own limits
Unusually for a public dashboard, the constraints are stated on the board itself: Polymarket's API returns at most 100 markets per call, so the queries page through it with an offset; markets below $50,000 in volume are filtered out to cut noise and stay inside the per-execution API limits; markets the API does not return are labelled No Data rather than dropped silently; a materialised view refreshes daily; and the charts are deliberately trimmed while the tables underneath carry the full population. Each of those is documented in Method Notes & Limitations below, and they are the first thing to read before quoting a number from the board.
Who it is for
- Prediction-market researchers who need per-market and per-outcome attribution rather than a venue total.
- Trading and data teams using prediction-market activity as an alternative-data signal.
- Analysts and journalists who need to cite a market-level figure and show where it came from.
- Dune users who want a working reference implementation of LiveFetch — the queries are public and can be copied.
What it is not
This is an analytics board, not a venue: it does not take orders, hold funds or quote prices. Bitnxt is not affiliated with Dune, Polymarket or the dashboard's author. For whole-venue Polymarket totals the board itself points readers to a separate rchen8 dashboard; the value here is the grain below it.





































