What it is
Polygonscan is the block explorer for the Polygon PoS chain: a free, no-account-required view of every block, transaction, contract, token and event on that network. It is part of the Etherscan family, so it runs on the same platform and infrastructure as the Ethereum explorer, and its API subscriptions are sold through Etherscan as one key covering more than sixty EVM chains, with the chain chosen by a parameter rather than by a separate product.
For this directory the significance is narrower and more useful than "block explorer". Polymarket settles on Polygon. That means the parts of a prediction market that are usually invisible — the collateral actually moving, the positions actually held, the oracle actually resolving a market — are all readable here, at the level of individual transactions.
Why it matters for prediction markets
Almost every other tool in this directory gives you a number someone else computed: a volume total, a price, a portfolio value. Polygonscan gives you the raw record those numbers are derived from. When a market resolves and someone claims it was wrong, the resolution call is here. When a large position appears from nowhere, the trades behind it are here. When a venue's analytics show volume that looks impossible, the collateral transfers either exist here or they do not.
It is also the only place where you can check a contract before you approve it. Prediction markets ask users to sign approvals and interact with contracts whose behaviour is not obvious from the interface; the explorer shows whether the source code was published, what the contract's read functions say about its state, and what the approval you already granted actually permits.
What Polymarket looks like on Polygonscan
Etherscan's metadata layer labels Polymarket's infrastructure by name rather than leaving it as anonymous hex, and that is what makes the explorer usable for this purpose. The exchange contract appears as a named Polymarket entry with verified source code, and the oracle adapters that resolve markets appear as their own named contracts, including a current version and an older one still holding traffic — so a reader can tell which adapter a given market's resolution went through.
Those adapter pages are more instructive than they first look. Their decoded activity reads as the lifecycle of prediction markets in plain method names: updates posted into the contract, resolution calls arriving from the oracle's addresses, and position redemptions coming in from user wallets afterwards. In other words, the abstract idea of "a market resolves and winners redeem" is visible as three different kinds of call into one contract, each with its own sender, block number and gas cost.
Following a whale — and knowing the limits of it
The explorer is the standard route for checking what a large trader actually did, and it is a good one, but it is a primary record rather than a whale-tracking product. What you can establish here is factual: which transactions an address sent, which positions it acquired or redeemed, what its current token holdings are, and whether the trades its followers attribute to it really exist on chain.
What you cannot establish is who is behind the address. A profitable-looking wallet may be a market maker's inventory, an internal account, a contract in a bundle of related contracts, or one of several addresses controlled by the same operator — and the explorer will label all of them simply as addresses. Treat any "whale" claim built purely on one address with more caution than the dashboard presenting it suggests, and cross-check the counter-party patterns before drawing conclusions about skill.
Verification, which is the real reason to be here
Three habits make the explorer genuinely useful rather than decorative. Read a contract's verification status and source before approving it, and be suspicious of anything unverified that claims to be part of a market. Check what approvals your wallet has already granted, and understand what each one lets a contract do. And when a transaction fails or does something unexpected, open the decoded input and the emitted logs — the answer is almost always in the event data rather than the interface.
The API, briefly
Everything visible on the site is available programmatically through one key: balances, transactions, transfers, contract source, logs and network statistics, on Polygon and dozens of other chains, selected with a chain parameter. The free tier is real but limited, the paid tiers start modestly and climb steeply, and the address-label product that makes "Polymarket: ..." possible is sold under its own gating. Details, limits and the parts where the vendor's own documentation disagrees with its pricing page are set out below.
Where it sits in this directory
Think of the layers. Venue APIs give you markets and execution. OddsPapi gives you cross-venue prices. DefiLlama gives you aggregate measurement of venues over time. Polygonscan sits underneath all of them as the settlement record: the place you go to confirm that something really happened, and the only one of the four that is a primary source rather than a derived one.
What it does not cover
Three boundaries are worth knowing. Polygon PoS and the Amoy testnet are what this explorer covers; Polygon's zkEVM network has its own separate explorer, so a contract there will not be found here. Polymarket's order book runs off chain, so the explorer shows settlement and positions rather than the quotes behind them. And gas is paid in POL, not MATIC — the token was migrated — which is why guides still referring to MATIC for Polygon fees are out of date rather than merely old-fashioned.





































