Polymarket does not publish one tidy “resolution history” archive you can browse. The record exists, and it is unusually complete — every proposal, dispute, and final settlement is written to a public blockchain — but it is spread across the market page, an oracle dashboard, and on-chain data, and each of those shows you a different slice.
This guide covers the four places to look, what the fields in an oracle record actually mean, how to pull up your own resolved positions, and what the most instructive past resolutions can teach you about which markets to avoid.
If you want the mechanics of how settlement works rather than how to look it up, read Polymarket Resolution Rules: The UMA Optimistic Oracle Explained first. New to the platform entirely? Start with What Is Polymarket?.
Where does Polymarket keep resolution history?
In four places, each useful for a different question:
| Where | Best for | Depth |
|---|---|---|
| The market page on Polymarket | ”How did this one market end?” | Final outcome and the rules it was graded against |
| The UMA oracle dapp | ”Who proposed it, was it disputed, when?” | Full proposal and dispute record per request |
| On-chain data on Polygon | ”Show me the immutable receipt” | Every transaction, permanently |
| A resolved-markets timeline in an alerts app | ”What resolved this week across a category?” | Browsable history across many markets |
The short version: the market page tells you the answer, the oracle tells you the story, and the chain proves it.
Method 1: The market page
The fastest check. Open the market and look for two things.
The outcome banner shows the final result on a settled market, and during the challenge window it shows a proposed outcome with the countdown still running — which is your signal that the result is not yet locked.
The Rules section, usually below the order book, holds the criteria the market was graded against. This matters more than people expect when reviewing history: an outcome that looks wrong at a glance is often perfectly consistent with wording you never read. The rules section also generally carries a link straight to that market’s entry in the UMA oracle, which is your bridge to Method 2.
Limitation: the market page shows you the destination, not the route. It will not tell you whether the result was contested, who proposed it, or how close the vote was.
Method 2: The UMA oracle dapp
oracle.uma.xyz is the closest thing to a real resolution history browser. Because Polymarket settles through UMA’s Optimistic Oracle, every market that goes through it leaves a request record there.
For any given request you can see the proposed outcome, the address that proposed it, the bond posted, whether a challenge was filed, the state of the challenge window, and — for anything that escalated — the token-holder vote and its result. The dapp separates live requests from settled ones, so you can either monitor what is happening now or dig through what already finished.
This is where you go when the question is “was this contested, and by whom?” It is also where you would file a dispute yourself, though be clear-eyed that doing so means posting a bond you forfeit if you lose.
Method 3: On-chain records on Polygon
Everything above is ultimately a friendly view of blockchain data. Polymarket’s settlement runs on Polygon, so proposals, disputes, and final resolutions all exist as transactions you can inspect directly on a block explorer, timestamped and permanent.
Most traders never need this. It becomes worth the effort in three situations: you are reconstructing exact timing for a post-mortem, you are auditing a specific proposer’s track record across many markets, or a front-end is showing you something you want to verify independently.
For anyone building tooling, Polymarket also maintains public data infrastructure — a resolution subgraph and a documented API — that expose the same records programmatically, including status transitions like proposed, disputed, re-proposed, and resolved. The official Polymarket developer documentation is the place to start rather than any third-party description of it, since endpoints and field names change.
Method 4: A browsable timeline of resolved markets
The three methods above all answer questions about a market you have already identified. They are poor at the broader question: what resolved recently in the categories I care about?
That is what the Timeline in Polymarket Alerts is for — a history of closed and resolved markets with topic filters, so you can review outcomes across a whole category rather than one URL at a time. The separate Disputes section tracks markets where an outcome is currently being challenged, with search and filtering, so a contested market you hold does not reach you hours late. The Features page shows both alongside price, whale, and user-activity alerts.
The practical difference is timing. Checking the oracle dapp is something you do after you already know there is a problem. A notification is what tells you there is one.
How to check your own resolved positions
For your personal history rather than the market’s, use your Polymarket portfolio and activity views. Your trade history shows entries and exits, and resolved positions show what each redeemed for.
Worth doing periodically, because this is where you find out something the market pages will not tell you: which categories of market you keep getting graded against unfavorably. Traders who review their own resolution history usually discover their losses cluster — in one sport, one type of political question, or one recurring wording pattern — far more than they cluster in bad luck.
Reading an oracle record: what the fields mean
Oracle and subgraph records use a small vocabulary that is not self-explanatory:
- Initialized — the resolution request exists, but nobody has proposed an answer yet.
- Proposed — an outcome has been submitted with a bond. The challenge window is running.
- Disputed / Challenged — someone posted a matching bond against the proposal.
- Re-proposed — a fresh proposal after a first dispute voided the original.
- Resolved — final and immutable.
- Proposed price vs. final price — the outcome as first submitted versus what actually settled. When these differ, a dispute changed the answer. That is the single most interesting comparison in the whole record.
- Was disputed — a flag worth scanning across many markets, because it tells you which question types generate contests.
A record where the proposed price and final price match, with no dispute flag, describes the overwhelming majority of markets: someone proposed the obvious answer and nobody objected.
Past resolutions worth studying
A handful of contested resolutions have become reference points, and each isolates a different failure mode. They are worth knowing not as trivia but because the patterns repeat.
The Ukraine minerals market, March 2025. A roughly $7 million market on whether Ukraine would agree to a minerals deal with the Trump administration resolved Yes despite no agreement having been signed, after a large UMA token holder voted a substantial share of the total across multiple wallets. Polymarket acknowledged the market had resolved too soon but declined to refund traders. The lesson is about governance concentration: when a dispute goes to a token-weighted vote, the distribution of that token becomes part of your risk. This episode directly drove the tightening of who is allowed to propose outcomes.
The Zelenskyy suit market, July 2025. With roughly $200 million in volume, a market on whether Volodymyr Zelenskyy would wear a suit resolved No even though mainstream outlets had described the outfit as one. Set aside who was right. The lesson is about subjective wording: the contract asked a question with no mechanical answer and provided no tiebreaker, which guaranteed that somebody would feel robbed regardless of the verdict. Markets that hinge on interpretation carry a risk that the price does not reflect.
The Barron Trump market, 2024. Polymarket overrode the oracle result and refunded traders, publicly calling the outcome wrong. The lesson is about how little you can rely on that happening. It is the exception that proves the rule — the company declined to intervene in the Ukraine case months later. Never size a position on the assumption someone will step in.
The common thread across all three: none of them were surprises hiding in the news. Each was visible in the contract structure before trading began — subjective criteria, a single oracle with no fallback, and ambiguous timing.
Turning history into a pre-trade filter
Resolution history is only worth reading if it changes what you do next. Three ways it can:
Check the base rate for the category. Some question types get disputed far more than others. Sports with clean official results almost never do. Geopolitical questions with soft criteria do so regularly. If the category you are about to trade has a contested past, treat the resolution stage as a real risk rather than a formality.
Read the wording against known failure modes. Once you have seen how “wore a suit” played out, undefined descriptors read very differently. So do undefined time zones, named sources with no fallback, and data that gets revised after first publication.
Watch the proposal, not just the event. For a position you are holding into settlement, the challenge window is roughly two hours. Knowing where the record lives is no help if you check it the next morning.
Frequently asked questions
Does Polymarket have a resolution history page? Not as a single browsable archive. Individual market pages show their own outcome, and the full proposal-and-dispute record lives in the UMA oracle dapp and on-chain on Polygon.
How can I see if a Polymarket market was disputed? Look up the market’s request on oracle.uma.xyz. The record shows whether a challenge was filed, by whom, and how it was ultimately settled.
Can a resolved market’s outcome be changed afterwards? No. Once finalized on-chain it is immutable. Polymarket has rarely issued refunds around outcomes it disagreed with, but the on-chain record itself does not change.
How do I find out why a market resolved the way it did? Read the market’s Rules section first — most surprising outcomes are consistent with wording that was not read carefully. If it went to a vote, the debate and evidence happen publicly in UMA’s Discord channels.
Where can I see my own resolved Polymarket positions? In your Polymarket portfolio and activity history. For a broader view across markets you did not trade, a resolved-markets timeline with topic filters is more practical.
Related reading
- Polymarket Resolution Rules: The UMA Optimistic Oracle Explained — bonds, timers, and the four dispute verdicts.
- How Polymarket Resolution Works — the shorter conceptual overview.
- Watchlists and Timeline on Polymarket — building a repeatable monitoring routine.
- Polymarket Trading Basics — liquidity and exit planning ahead of settlement.
Bottom line
The resolution record on Polymarket is more transparent than on almost any comparable venue — it is just scattered. The market page gives you the outcome and the criteria, the UMA oracle dapp gives you the proposal and dispute trail, the Polygon chain gives you the permanent receipt, and a filtered timeline gives you the overview. Learn to read the proposed price against the final price, study the handful of resolutions that went badly, and use what they show you as a filter on what you trade next rather than a story you tell afterwards.
This article is educational and independent. Interfaces and data endpoints change — verify current details in the official Polymarket and UMA documentation.