BTCBTC$64,716-1.19%|
ETHETH$1,810.75-1.42%|
USDTUSDT$0.99950+0.01%|
BNB$590.3700-1.12%|
USDCUSDC$0.99970+0.01%|
XRPXRP$0.95765-1.36%|
SOLSOL$71.2600-3.33%|
TRXTRX$0.30599-1.15%|
FIGR_HELOCFIGR_HELOC$1.0570+1.02%|
HYPEHYPE$67.2300-0.37%|
ZECZEC$891.1400+2.11%|
XMRXMR$499.1900-3.10%|
DOGEDOGE$0.05851-3.97%|
USDSUSDS$0.99945-0.04%|
LEOLEO$9.1500-1.53%|
WBTWBT$62.6100-1.86%|
LINKLINK$9.2100-0.43%|
ADAADA$0.15325-2.31%|
USDEUSDE$0.99948+0.02%|
XLMXLM$0.13880-0.51%|
DAIDAI$0.99981+0.00%|
BCHBCH$208.0900-1.77%|
NEARNEAR$3.1300-2.48%|
LTCLTC$44.7900-3.09%|
CCCC$0.08263+0.96%|
AVAXAVAX$7.1600-6.49%|
UNIUNI$5.1200-0.31%|
USD1USD1$0.99806+0.00%|
XAUTXAUT$3,818.71-0.23%|
GRAMGRAM$1.0500-0.33%|
BTCBTC$64,716-1.19%|
ETHETH$1,810.75-1.42%|
USDTUSDT$0.99950+0.01%|
BNBBNB$590.3700-1.12%|
USDCUSDC$0.99970+0.01%|
XRPXRP$0.95765-1.36%|
SOLSOL$71.2600-3.33%|
TRXTRX$0.30599-1.15%|
FIGR_HELOCFIGR_HELOC$1.0570+1.02%|
HYPEHYPE$67.2300-0.37%|
ZECZEC$891.1400+2.11%|
XMRXMR$499.1900-3.10%|
DOGEDOGE$0.05851-3.97%|
USDSUSDS$0.99945-0.04%|
LEOLEO$9.1500-1.53%|
WBTWBT$62.6100-1.86%|
LINKLINK$9.2100-0.43%|
ADAADA$0.15325-2.31%|
USDEUSDE$0.99948+0.02%|
XLMXLM$0.13880-0.51%|
DAIDAI$0.99981+0.00%|
BCHBCH$208.0900-1.77%|
NEARNEAR$3.1300-2.48%|
LTCLTC$44.7900-3.09%|
CCCC$0.08263+0.96%|
AVAXAVAX$7.1600-6.49%|
UNIUNI$5.1200-0.31%|
USD1USD1$0.99806+0.00%|
XAUTXAUT$3,818.71-0.23%|
GRAMGRAM$1.0500-0.33%|
Polygonscan
Tool / APITier-2Block explorerVerified

Polygonscan

The Polygon PoS block explorer that labels Polymarket's own contracts — where market resolution, collateral and whale trades can actually be checked.

Visit website

Key Facts

CategoryBlock explorer
AccessBrowsing is completely free and needs no account. The API has a free tier that requires a key and attribution, and it is tighter than most guides suggest: as documented, 3 calls per second, up to 100,000 calls a day, community endpoints only, and coverage of selected chains rather than all of them. Paid tiers run Lite at $49 a month (5 calls a second, all chains, still community endpoints only), Standard at $199 (10 a second, 200,000 a day, Pro endpoints unlocked), Advanced at $299, Professional at $399 and Pro Plus at $899, with quarterly and yearly discounts of 10 and 15 percent respectively, plus enterprise and dedicated options. Two caveats matter before paying: the free tier's chain coverage was cut back in late 2025, so confirm Polygon is on the list before building on it, and address name tags — the labels that make Polymarket's contracts recognisable — sit behind the Address Metadata product, which the pricing page lists only from the Pro Plus tier upward even though the API documentation lists the same endpoint among ordinary Pro endpoints.
Venues CoveredPolymarket on Polygon, verified by its own labelled contracts — the exchange contract and the oracle adapters that resolve markets — plus every other contract on Polygon PoS, all of it queryable alongside 60-plus other EVM chains through one API key. Polygon zkEVM is a separate explorer, not this one.
Data ConfidenceVerified
Last Reviewed1 Oct 2026

What It Does

Polygonscan is the block explorer for the Polygon PoS chain, and because Polymarket settles there it doubles as the on-chain record for prediction market activity: every contract, trade, collateral transfer, position redemption and oracle resolution on the venue can be read here rather than taken on trust. It labels Polymarket's own infrastructure by name — the exchange contract and the oracle adapters appear as Polymarket entries rather than anonymous addresses — so a reader can find the resolution pipeline and follow it. The explorer also decodes what contracts actually did, lets you query event logs without writing code, verifies contract source before you interact with anything, and exposes the same data through one API key across 60-plus EVM chains with Polygon selected by chain ID 137. Browsing is free; the API has a free tier with hard limits and paid tiers above it, sold through Etherscan, whose family of explorers Polygonscan belongs to.

Overview

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.

How It Works

Reading a transaction the way an analyst does

A transaction page is dense, and the parts that matter for prediction market work are the decoded input, the logs, the internal transactions and the token transfers. The decoded input tells you which method the contract was called with and what arguments were passed — for a redemption that is the position being redeemed. The logs carry the events the contract emitted, which is where outcome data actually lives. Internal transactions reveal value moved by a contract rather than by the sender, which matters because most prediction market plumbing is contract-to-contract. And token transfers show collateral and position movements side by side, so a trade can be read without decoding the maths yourself.

Two practical notes. Value shown in POL is gas and fees, not the trade — the economic content of a prediction market transaction is almost always in the token transfers, not the native value. And a failed transaction still has a page, with a reason where the contract supplied one; a run of failures at the same address in the same block range usually means a bot losing a race, not a broken market.

Address and contract pages

Address pages carry the name tag, where one exists, the verified status of the contract, the balance with a dollar value, token holdings, and a tab for the contract itself with source code, ABI, read and write functions, and the events it emits. Where a contract sits behind a proxy, the page links the implementation, which is the contract whose code actually runs — checking that link is the difference between auditing a contract and auditing its wrapper.

The address page also carries a multichain section showing the same address's activity on other chains, which is how a wallet that operates on several networks can be seen as one entity without leaving the page. For a Polymarket trader who hedges elsewhere, that is the fastest way to see the whole footprint rather than the Polygon slice of it.

Advanced Filter, which is the underused tool

Advanced Filter queries logs by address, topic and block range through a form rather than code, and it answers the questions this directory actually cares about: every call into a resolution adapter over a period, every transfer of a particular outcome token, every event from a market's contract since it was deployed. Results export for offline work. For most readers this is the single most valuable feature on the site, because it turns the explorer from something you look things up on into something you run queries against.

Token pages, flows and holders

Token pages show supply, holders and a flow visualisation that maps where a token has moved between major addresses. Applied to the collateral used by a prediction market, that is a view of where the money in the market sat before it became positions; applied to an outcome token, it shows how concentrated a market's winning side is. Holder lists come with the caveat that contract addresses appear as holders too, since pooled positions and internal accounts legitimately hold large balances.

Gas, costs and the Input Data Decoder

The gas tracker reports a median gas price in Gwei with a dollar estimate, and it is the honest way to answer "what will this cost" before doing something in bulk — redeeming many small positions, or a scripted set of transfers. Polygon fees are low enough that they rarely change a strategy, but not so low that a badly written loop is free.

The input data decoder takes raw calldata you have from elsewhere — an API response, a log, an unsigned transaction — and turns it back into a readable call. It is the tool that makes a decoded-input habit practical when the payload arrives without the interface attached.

Approvals: the risk surface users forget

Any contract interaction that moves your tokens needs an approval, and prediction markets are no exception: buying, selling and redeeming all rest on approvals you granted earlier, often with no expiry. The explorer shows what your address has approved, to which contracts and for how much, and it can revoke them. The habit worth building is to check approvals after using a new venue rather than only when something looks wrong, and to be careful with revocation while a position is open — cutting an approval a market needs mid-flight can leave you unable to complete the action that justified it.

The API in practice

One key covers more than sixty EVM chains, and Polygon is selected with its chain identifier rather than through a separate endpoint, so the same integration works across networks with the parameter changed. The documented endpoint families that matter here are account-level history (transactions, internal transactions, token and NFT transfers, balances), event logs, contract metadata including source code and ABI, token supply and holders, and network statistics.

Pricing is tiered by throughput and by which endpoints you may call. The free tier is genuine but constrained — a low per-second ceiling, a daily cap, community endpoints only, selected chains only, and attribution required — and the jump to the entry paid tier buys back chain coverage rather than higher limits, which reflects the free tier's late-2025 cutback. Pro endpoints unlock further up the range, and the address metadata product sits above that again. One licence restriction is worth flagging for teams: the top metadata tier is limited to a single application licence, so multi-product shops need the enterprise tier instead.

For agents rather than applications, the same documentation covers building with an MCP server, a command-line client and packaged skills, so an AI assistant can query the explorer's data directly instead of scraping the interface. That route inherits the same key, limits and plan gating as any other API client.

Method Notes & Limitations

Where this page's facts come from

Everything here was read on 2026-10-01 from Polygonscan itself — the homepage, three address pages for contracts the explorer labels as Polymarket's, and the explorer's own tool pages for gas, advanced filtering, token flows and input decoding — together with Etherscan's API documentation, its rate-limit reference, its endpoint lists, its supported-chains page, its Polygon-specific API pricing page and its published notice about changes to the free tier. No account was created, no API key was requested and no API call was made; the free-tier and paid-tier figures below are the vendor's published numbers read from those pages, not tested limits.

Verified against primary sources

ClaimStatus
Polygonscan is the block explorer for Polygon PoS, with a separate Amoy testnet explorerVerified — stated on the explorer itself, including the network switcher
The explorer labels Polymarket's own contracts by name rather than leaving them anonymousVerified — labelled Polymarket contracts appear both on the homepage's trending list and on their own pages
Polymarket's exchange contract is verified, and its oracle adapters resolve markets on chainVerified — a labelled Polymarket exchange contract shows as verified, and adapter pages show decoded resolution and redemption calls
Contracts show decoded method names for the resolution lifecycleVerified — decoded activity on an adapter page reads as updates, resolutions and position redemptions
One API key covers 60+ EVM chains, with the chain selected by parameterVerified — API documentation and the pricing page
Free tier: 3 calls per second, 100,000 calls a day, selected chains, attribution required, no Pro endpointsVerified — API documentation and pricing page agree
Free-tier chain coverage was reduced in late 2025Verified — the vendor's own published explanation, which also introduces the discounted entry tier
Paid tiers and their limitsVerified from the pricing page, with one inconsistency between the docs and the pricing page on metadata access — see below
Whether any of these figures hold on the day you read thisNot claimed — prices, gas and network statistics all change, and only dated observations are used above

Three places the numbers do not quite agree

The free tier's per-second ceiling is published as 3 calls a second in the vendor's documentation and pricing page, while several independent 2026 guides still describe it as 5 calls a second. That older figure now matches the entry paid tier rather than the free one, so anyone sizing an integration from a third-party article should re-check against the vendor. Second, access to the address metadata endpoint — the one behind name labels like the Polymarket entries — is listed among ordinary Pro endpoints in the documentation but appears on the pricing page only from the higher metadata tier, at a considerably higher monthly price; confirm which applies before subscribing for labels alone. Third, the free tier's chain coverage is described as roughly ninety percent of supported chains, and it changed in late 2025, so the list rather than the percentage is what should be checked.

What this page does not claim

It does not audit the accuracy of the explorer's data, and a label is not an endorsement: the Polymarket name tags come from the explorer's metadata layer, which is useful precisely because it is provider-maintained, but a label describes what a contract is called rather than whether a project is sound. It does not assert that any address discussed above belongs to a particular person or firm — attribution beyond what the explorer itself labels would be speculation. And it does not present whale-following as a strategy: the explorer can confirm what an address did, not whether copying it would have made money.

Editorial note

Bitnxt is not affiliated with Polygonscan or Etherscan, has no commercial relationship with either and receives nothing from them; the visit link on this page carries a tracking parameter only so that referrals can be counted, and no commission is earned. Worth knowing when reading the interface: the explorer carries third-party advertising, including promotion of the API product itself, so sponsored placements appear in the same frame as the data. Nothing here is investment advice, and the API figures quoted are the vendor's published plans rather than a recommendation to buy any of them.

Venues Covered

Polymarket on Polygon, verified by its own labelled contracts — the exchange contract and the oracle adapters that resolve markets — plus every other contract on Polygon PoS, all of it queryable alongside 60-plus other EVM chains through one API key. Polygon zkEVM is a separate explorer, not this one.

Access & Pricing

Browsing is completely free and needs no account. The API has a free tier that requires a key and attribution, and it is tighter than most guides suggest: as documented, 3 calls per second, up to 100,000 calls a day, community endpoints only, and coverage of selected chains rather than all of them. Paid tiers run Lite at $49 a month (5 calls a second, all chains, still community endpoints only), Standard at $199 (10 a second, 200,000 a day, Pro endpoints unlocked), Advanced at $299, Professional at $399 and Pro Plus at $899, with quarterly and yearly discounts of 10 and 15 percent respectively, plus enterprise and dedicated options. Two caveats matter before paying: the free tier's chain coverage was cut back in late 2025, so confirm Polygon is on the list before building on it, and address name tags — the labels that make Polymarket's contracts recognisable — sit behind the Address Metadata product, which the pricing page lists only from the Pro Plus tier upward even though the API documentation lists the same endpoint among ordinary Pro endpoints.

Frequently Asked Questions

Sources & Verification

The factual claims on this page were checked against the sources below.

Bitnxt uses cookies to run the site, understand how it is used, and measure ads. You can accept or decline below, and change your choice any time in our Privacy Policy.