Polygon transaction & wallet explorer

This free Polygon transaction explorer lets you check any tx hash, wallet address, block or token on Polygon PoS mainnet in a couple of seconds. Paste what you have into the search box above, and you get the status, fee, token transfers and a shareable receipt, pulled live from the chain, with no account and nothing stored on our side.

We built this tool because we kept doing the same thing during our explorer reviews: open three tabs, paste the same hash three times, and piece together a readable answer for someone who just wanted to know "did my USDC arrive?". The Polygon explorer on this page tries to answer that question on one screen, then hands you links to verify it on the bigger explorers if you want the full forensic picture.

How to look up a Polygon transaction, address, block or token

The search box understands four kinds of input and works out which one you pasted. You don't need to pick a mode.

Not sure what to try? The "Try an example" chips load a sample transaction, a wallet, the latest block and the native USDC token contract, so you can see what each result looks like before you paste your own data. Below the search results, the latest blocks and latest transactions refresh automatically, which doubles as a quick live dashboard for Polygon mainnet.

Polygon tx hash lookup

A Polygon transaction hash always starts with 0x and is followed by 64 hexadecimal characters: 66 characters in total. Your wallet shows it after you send (MetaMask calls it "Transaction ID" under activity details; exchanges often call it "TxID" or "Txn hash"). Copy it in full. A single missing character means no match. If you want a slower walkthrough of each field, our guide to checking a Polygon transaction goes through a real USDC transfer line by line.

Polygon address explorer: wallets and contracts

Paste any 42-character address (0x plus 40 characters) to open it as a wallet view. You'll see the POL balance with its current USD value, every token the address holds with USD prices where they're known, the total transaction count, and a recent activity list where each row is labelled IN, OUT or SELF. "Load more" pages further back in history. If the address is a smart contract, the card adds contract details such as verification status and creator. For long-term monitoring of a wallet, read how to track a Polygon wallet.

Blocks and tokens

A block number opens the block view: the validator that produced it, gas used against the gas limit, the base fee, burnt fees and the list of transactions inside. A token contract or name opens the token view with price, market cap, holder count, total supply and recent transfers. Searching by name is handy, but for stablecoins always confirm the contract, because scam tokens copy names and symbols. Our USDT and USDC tracker page lists the genuine addresses.

What every field on the result card means

Polygon uses the same transaction format as Ethereum, so the field names match what you'd see on Etherscan-style explorers. Here is a plain-English reference.

A few fields trip people up. Value only shows native POL. If you sent USDT, value is usually 0 POL, and the actual payment sits under Token transfers, which is why the receipt card pulls the main token movement to the top for you. To is often a contract rather than a person: for a token payment, the "To" field is the token contract, and the real recipient appears inside the token transfer line.

Failed transactions still cost a fee. The network did the work of running your transaction until it reverted, so gas was consumed. The most common reasons we see are slippage limits on swaps, expired deadlines and insufficient token allowance. Pending means the transaction is known to the node but not yet in a block; on Polygon that normally lasts a few seconds. If it stays there, head to the mempool and pending transaction page for ways to speed up or cancel it.

Confirmations matter less than they used to. Since the Heimdall v2 upgrade in July 2025, Polygon PoS reaches deterministic finality in roughly five seconds, so a transaction a few blocks deep is effectively final. The fee in POL is usually a fraction of a cent; the live Polygon gas tracker shows what current prices mean for a transfer, a swap or an NFT mint.

Nonce is simply a counter: your first transaction from a wallet has nonce 0, the next has 1, and so on. It's the field to check when a transaction is stuck, because a later transaction can't be mined until every lower nonce is confirmed or replaced.

Networks supported: PoS, Amoy and zkEVM

The tool covers three networks, with different depth of data.

• Polygon PoS mainnet (chain ID 137): full mode. Transactions, addresses, blocks and tokens come from the Blockscout API v2, including decoded methods, token transfers, token balances and USD values. If Blockscout is slow, core transaction data falls back to a public JSON-RPC node.
• Amoy testnet (chain ID 80002): RPC mode. You get status, sender, recipient, value, fee, gas and block for test transactions. Handy when you're deploying contracts and want a quick check without leaving this site.
• Polygon zkEVM (chain ID 1101): RPC mode, for historical lookups. The zkEVM Mainnet Beta has been sunset in 2026, so treat this as a best-effort archive view while public endpoints remain available.

In RPC mode a small amber note appears to remind you that only basic data is shown. That is expected, not an error. For deeper background on each chain, see our page on the Polygon PoS chain explorer, which also covers checkpoints and system contracts.

Sharing a result: links, QR codes and payment receipts

Every lookup updates the page URL, so the address bar always holds a clean, shareable link such as /explorer/?tx=0x… or /explorer/?address=0x…&net=amoy. Open that link on any device and the same result loads fresh from the chain.

The Share button opens a small panel with:

• a copy-link field,
• one-tap shortcuts for Telegram, WhatsApp, X and email,
• a QR code you can show on screen, which is useful at a shop counter or when someone wants to check a payment from their phone,
• the phone's native share sheet on mobile devices.

The payment receipt card at the top of every transaction is the part we designed for non-technical people. It shows the status badge, the amount (native POL or the main token moved), a USD estimate, sender, recipient, time, fee, block and confirmations in a layout that reads like a receipt. Print / save PDF turns the card into a clean one-page document without the navigation around it. Freelancers use it to attach proof to an invoice; support teams use it to settle "I sent it, you didn't receive it" conversations. There's a full walkthrough in our guide to verifying and sharing a payment.

Privacy: what we store (nothing)

There is no account, no API key and no server of ours in the middle. When you search, your browser sends the request directly to public infrastructure: Blockscout's API for Polygon PoS and public RPC nodes such as publicnode, dRPC and 1RPC. Token prices come from a public price API. We don't log your queries, we don't build a history of the wallets you look up, and we don't need your wallet connected, ever.

Two honest caveats. First, the third-party APIs you query can see your IP address, like any website you visit. Second, blockchain data itself is public by design: anyone can look up any address. If privacy matters to you, the explorer can't change that; only how you use addresses can.

Where the data comes from

Our explorer is a thin, fast interface on top of open data sources, and we think you should know exactly which ones.

The main source for Polygon PoS is the Blockscout REST API v2 at polygon.blockscout.com/api/v2/, run by the open-source Blockscout project. Endpoints like /transactions/{hash}, /addresses/{address}/token-balances and /blocks/{number} supply decoded data, token metadata and prices. The project's developer documentation describes these endpoints if you want to build on them yourself.

The second source is public JSON-RPC: the same interface wallets use to talk to Polygon nodes. We use it for the live block feed, as a fallback when Blockscout is busy, and as the only source on Amoy and zkEVM. One warning if you run your own scripts: the old polygon-rpc.com endpoint now returns an authentication error, so swap it for a working public node. Our explorer API and RPC page lists endpoints we tested.

How this tool differs from PolygonScan

PolygonScan, built by the Etherscan team, is the most complete Polygon explorer and the one we rank first in our list of the best Polygon explorers. We're not trying to replace it. Here's where each one fits.

In short: use this page when you want an answer and a shareable proof in ten seconds. Use PolygonScan when you need to verify a contract, revoke approvals, export history for your records or dig through internal transactions. If you prefer open-source tooling with a keyless API, the Blockscout explorer itself is excellent. Every result here has "Verify on" buttons that open the same query on PolygonScan, Blockscout and OKLink, so moving between them costs one click.

Troubleshooting: not found, pending, wrong network

Most failed lookups come down to a handful of causes. Work through them in this order.

"Nothing found for this query"

Check the network tab first. An Amoy test transaction won't show up on PoS mainnet, and vice versa. Then check the chain: Polygon, Ethereum, Arbitrum, Base and BNB Chain all use identical-looking 0x hashes and addresses. If you withdrew from an exchange, the withdrawal page shows which network was used. If it says ERC-20 or Ethereum, the transaction lives on Ethereum and you need an Ethereum explorer, not a Polygon one.

Ethereum hash vs Polygon hash

There's no way to tell them apart by looking. Both are 0x plus 64 characters. The same wallet address even exists on both chains, which is why people are often confused when their "Polygon" balance appears empty: the funds went to the same address on Ethereum. If a hash isn't found here or on PolygonScan, try it on Etherscan. Bridge transfers are a special case, with one transaction on each chain; our bridge explorer page explains how to follow both halves.

Stuck on pending

Polygon produces a block roughly every two seconds, so "pending" for more than a minute usually means your gas price was too low when fees spiked, or an earlier transaction from the same wallet is still waiting (nonces must go in order). Speed it up or cancel it from your wallet by resending with the same nonce and a higher fee.

Balance looks wrong

Token balances come from the indexer and can lag a few seconds behind a brand-new transfer. Spam tokens airdropped to your wallet may also appear. They're harmless if you don't interact with them, but never visit websites named in a token's name. And if you still need POL for gas or USDC to pay someone, buy it on a regulated exchange that holds licences in several jurisdictions and lets you withdraw directly to Polygon. Double-check the withdrawal network is Polygon PoS, not Ethereum, before you confirm.

The data source did not respond

Public APIs occasionally rate-limit or hiccup. Wait a few seconds and search again; the tool automatically tries other RPC endpoints. If a result looks inconsistent, the "Verify on" buttons are the quickest way to get a second opinion from an independent explorer. For a view of how Polygon's architecture fits together, the official Polygon documentation is the best starting point.