A Polygon Amoy explorer lets you look up transactions, addresses and contracts on Amoy, the Polygon PoS testnet (chain ID 80002). The main option is Amoy PolygonScan at amoy.polygonscan.com, with OKLink as a second choice. For quick checks, our live explorer has an Amoy tab. Test POL comes free from the Polygon faucet.
We deploy to Amoy regularly while testing tools for this site, and most of the problems we hit are not about Solidity at all. They're wrong chain IDs, dead RPC endpoints, empty faucets and explorers opened on the wrong network. This guide is organised around those real-world snags.
What is the Amoy testnet?
Amoy is the public testnet for Polygon PoS. It runs the same software stack as mainnet (Bor for execution, Heimdall for consensus and checkpoints), but its checkpoints go to Ethereum's Sepolia testnet instead of Ethereum mainnet. Gas is paid in test POL, which you get for free and which has no market value.
Polygon launched Amoy in late 2023 to replace Mumbai, the old testnet that depended on Goerli. When Goerli was shut down, Mumbai was deprecated in April 2024. If you still have Mumbai in your configs, our page on what happened to the Mumbai explorer has a migration checklist.
Because Amoy tracks mainnet upgrades, new PoS features usually appear there first. That makes it the right place to test anything that touches gas behaviour, account abstraction or contract deployment before you ship to chain 137.
Polygon Amoy block explorers compared
We tested three ways to explore Amoy in September 2026 with the same test deployment: a simple ERC-20 contract, a verification, and a few transfers.
| Explorer | Verify contracts | Best for |
|---|---|---|
| Amoy PolygonScan | Yes | Full dev workflow |
| OKLink Amoy | Limited | Second opinion |
| Our Amoy tab | No | Fast status check, sharing |
Amoy PolygonScan is the default Polygon testnet block explorer. It mirrors the mainnet PolygonScan interface: transactions, internal transactions, token transfers, event logs, contract source code, and the Read/Write Contract tabs that let you call functions from the browser. This is where you'll spend most of your time. Our full PolygonScan review applies almost one-to-one.
OKLink indexes Amoy too, at a separate Amoy section of its Polygon explorer. It's handy when PolygonScan is slow or you want to confirm that a transaction propagated.
Our live explorer's Amoy tab reads straight from a public Amoy RPC node. It shows status, from, to, value, fee, gas and block, but not decoded token transfers. Its real advantage is the share link: paste a test transaction, press Share, and send teammates or QA a link that opens the same result.
Amoy explorer URL and network settings
For wallets, Hardhat or Foundry you'll need the RPC and explorer URLs. We keep the full, tested list on the Polygon network settings page, including one-click "Add to MetaMask" for Amoy, so we don't duplicate it here. The short version:
| Setting | Value |
|---|---|
| Network name | Polygon Amoy |
| Chain ID | 80002 |
| Currency symbol | POL |
| Block explorer URL | https://amoy.polygonscan.com/ |
| Public RPC (tested) | polygon-amoy-bor-rpc.publicnode.com |
| Alternative RPC | polygon-amoy.drpc.org |
Always add https:// in front of the RPC host names. For production-grade testing you'll want a provider endpoint with your own key; our explorer API and RPC guide compares options.
Amoy faucets: getting test POL
You need test POL to pay gas on Amoy. There are two routes.
The official Polygon faucet at faucet.polygon.technology sends small amounts of Amoy POL. It uses anti-bot checks, and it limits how often one address or account can claim. In our experience, it's enough for dozens of deployments of small contracts, but not for load testing.
Third-party faucets from infrastructure providers such as Alchemy and QuickNode also pay out Amoy POL. Many now ask you to sign in with a free account, or hold a small balance on a mainnet to prove you're not a bot farm. Faucet rules change often, so if one is dry, try another rather than waiting.
Test POL is not real POL, and it can't be sold or bridged to mainnet. When you're ready to go live and need real POL for mainnet gas, buy it on a regulated exchange that holds licences in several jurisdictions and supports direct withdrawals to Polygon PoS, then send it to your deployer wallet. Our Polygon gas tracker shows what mainnet deployments currently cost.
Deploying and verifying contracts on Amoy
Here's the workflow we use. It works with Hardhat, Foundry or Remix.
- Configure the network. Add Amoy with chain ID 80002 and a working RPC URL to your config. In Foundry that's an
[rpc_endpoints]entry; in Hardhat, a network block withchainId: 80002. - Fund the deployer. Claim test POL from the faucet to the wallet whose private key your tool uses. Keep that key in an environment variable, never in the repo.
- Deploy. Run your deploy script. Copy the contract address and deployment transaction hash from the output.
- Check it on the explorer. Open the hash on Amoy PolygonScan or in our explorer's Amoy tab. Status should be Success, with "Contract Creation" or your contract address in the To field.
- Verify the source. Use an Etherscan API V2 key with chain ID 80002. In Foundry:
forge verify-contract <address> <Contract> --chain 80002. In Hardhat, the verify plugin with the Amoy network. Or paste flattened source into PolygonScan's verification form. - Interact. Once verified, PolygonScan's Read and Write Contract tabs let you test functions from the browser with your connected wallet.
Verification fails most often because of a compiler version or optimizer mismatch. Make sure the settings you submit match exactly what you compiled with, including the number of optimizer runs and any constructor arguments. Etherscan's API documentation lists the supported chains and parameters for V2 keys.
Using the Amoy explorer to debug your contracts
A block explorer is one of the most underrated debugging tools you have on a testnet. Once a transaction is on Amoy PolygonScan, you can see far more than "Success" or "Fail".
Event logs. The Logs tab lists every event your contract emitted, decoded if the contract is verified. If your frontend isn't updating, check whether the event actually fired and with which arguments. Nine times out of ten the bug is in the listener, not the contract.
Internal transactions. When one contract calls another, or sends POL as part of a function, those calls appear as internal transactions. They're how you confirm that a payout, a refund or a factory deployment really happened.
Revert reasons. For failed transactions, PolygonScan often shows the revert message, such as a custom error or a require string. If it doesn't, replay the transaction in a debugger. Tenderly supports Polygon networks and gives a line-by-line trace; our page on other Polygon explorers and dev tools covers it.
Gas used vs limit. Compare the two on every important function. A function that uses nearly 100% of its limit on Amoy is a warning sign, because mainnet state and inputs can push it over the edge.
Token tracker. Deploy a test ERC-20 or NFT and PolygonScan creates a token page with holders and transfers. It's a quick sanity check that your mint and transfer logic produces the balances you expect.
We also recommend sharing explorer links in pull requests and bug reports rather than pasting raw hashes. A link to the exact Amoy transaction lets a reviewer see inputs, logs and the revert reason in one click.
Common Amoy errors and how to fix them
These are the errors we and our readers hit most often on the Polygon Amoy testnet, roughly in order of frequency.
"Insufficient funds for gas * price + value." Your wallet has no test POL, or not enough for the gas limit your tool set. Hit the faucet, or reduce the gas limit if your tool is massively over-estimating.
"Transaction underpriced." Polygon nodes enforce a minimum priority fee, and some tools default to a tip that's too low. Let the tool estimate fees from the network, or raise the priority fee manually.
"Chain ID mismatch" or wrong-network errors. Something in your setup still says 80001 (Mumbai) or 137 (mainnet). Search your config, .env files and wallet network list for old values.
RPC errors, timeouts or authentication failures. Public endpoints come and go. Old tutorials point to Mumbai or to polygon-rpc.com, which now returns an auth error. Switch to one of the tested endpoints above or your own provider key.
"Nonce too low" / stuck transactions. Usually caused by restarting a script while a transaction was pending, or using the same key from two tools at once. Wait for pending transactions to confirm, or reset the account nonce in your wallet's advanced settings. Our pending transaction guide explains the nonce mechanics.
Transaction not on the explorer. Make sure you opened amoy.polygonscan.com, not the mainnet site, and that the transaction was actually broadcast. If your script crashed before sending, there's nothing to find.
Amoy vs mainnet: what's different
Amoy behaves like mainnet in almost every technical way, which is the point. The differences worth remembering: test POL is free and worthless; faucet limits constrain large tests; activity is far lower, so gas prices and block fullness don't reflect mainnet conditions; and some mainnet tokens and protocols simply don't exist on Amoy, so you'll deploy your own mocks. Data on Amoy can also be less stable over the long term than on mainnet, so don't treat testnet as permanent storage for anything.
When you're done testing, switch the chain ID to 137, verify again on mainnet PolygonScan, and look up your first live transactions in the Polygon PoS explorer guide or our live tool. For which mainnet explorer to use once you're live, see our ranking of the best Polygon explorers, and keep the Polygon team's developer documentation bookmarked for protocol changes that reach Amoy first.