To check a Polygon transaction, copy its 66-character hash (it starts with 0x) from your wallet, paste it into a Polygon explorer and read the status line: Success, Failed or Pending. Then check the sender, recipient, token transfers and fee. The whole check takes under three minutes, and this guide explains every field so you know what you are looking at.
Quick answer
Paste the tx hash into our live Polygon explorer, PolygonScan or Blockscout. “Success” plus a few confirmations means the transfer is done and irreversible. For USDT, USDC or any other token, ignore the POL “Value” line and read the token transfers section instead.
We tested every step here in September 2026 by following the same USDC transfer, a failed swap and a stuck transaction on three explorers. Screens differ a little between PolygonScan, Blockscout and our tool, but the underlying fields are identical because they all read the same chain.
Step by step: how to check a Polygon transaction
- Copy the transaction hash. In MetaMask, open Activity, tap the transaction and choose “View on block explorer” or copy the transaction ID. In Trust Wallet it's under the transaction details. On an exchange, look for “TxID” or “Transaction hash” in your withdrawal history.
- Paste it into a Polygon explorer. Use the search bar at the top of any page on this site, PolygonScan or Blockscout. Make sure Polygon PoS is selected, not Ethereum or Amoy.
- Read the status. Success, Failed or Pending. Nothing else on the page matters until you know this.
- Check From, To and token transfers. Confirm the sender and recipient, and find the real token amount in the transfers section.
- Review the fee. Look at the fee in POL, the gas price in gwei and how much of the gas limit was used.
- Confirm finality. Check the block number and confirmations. A few blocks on top means it's final.
Where to find your Polygon tx hash
The transaction hash is the receipt number of the blockchain. It's always 0x followed by 64 hexadecimal characters, 66 characters in total. An address is shorter (42 characters), and people often paste their own address by mistake. If you search an address, you'll land on a wallet page instead of a transaction, which is a useful hint that you copied the wrong thing.
Exchanges sometimes show only a shortened hash like 0x3f9a…c21b. Click it or use the copy icon to get the full value. If an exchange shows no hash at all, the withdrawal probably hasn't been broadcast yet; it may still be in internal review. In that case no explorer can find it, and only the exchange's support can tell you more.
A last trap: the same hash format is used on Ethereum, Base, Arbitrum and every other EVM chain. If an explorer says “not found”, try switching the network before you panic. Our tool has a network selector for Polygon PoS, Amoy and the archived zkEVM, and PolygonScan has separate sites for Amoy and zkEVM.
Reading every field of a Polygon transaction
Once the page loads, you'll see a list of fields. Here's what each one tells you, in roughly the order explorers show them.
Transaction hash confirms you are on the right transaction. Status is the result, covered in detail below. Block is the number of the block that included the transaction, and next to it you'll usually see the number of confirmations, meaning blocks added since. Timestamp is when that block was produced. Our tool shows it in both relative time and UTC, which helps when you're matching a payment against an invoice in another time zone.
From is the address that signed and paid for the transaction. To is the address it was sent to. For a simple POL transfer, that's the recipient. For a token transfer, a swap or an NFT mint, “To” is the smart contract being called, not the person receiving the tokens. That trips up many first-time users who think their USDT went to “the Tether contract” instead of their friend.
Value is the amount of native POL sent with the transaction, with a USD estimate. For token transfers it's usually zero. Token transfers (called “ERC-20 Tokens Transferred” on PolygonScan) list every token movement caused by the transaction: from, to, amount and the token contract. This is where you verify a stablecoin payment. Always click the token name and compare its contract address with the official one listed on our USDT and USDC explorer page, because fake tokens copy the name and symbol.
Transaction fee is what the sender paid, in POL. It equals gas used multiplied by the effective gas price. On Polygon PoS this is usually fractions of a cent for a simple transfer; the live number is on our Polygon gas tracker. Gas price is shown in gwei, a billionth of a POL. Gas limit and gas used show how much work the sender allowed versus how much the transaction actually needed. If gas used equals the limit exactly and the status is Failed, you are almost certainly looking at an out-of-gas error.
Nonce is the sender's transaction counter. The first transaction from an address has nonce 0, the next 1, and so on. Transactions from the same address must be processed in nonce order, which explains many “stuck” situations. Input data is the encoded instruction sent to a contract. Good explorers decode it into a method name such as transfer, approve or swapExactTokensForTokens, with readable parameters. Our explorer shows the decoded method when the contract is verified.
Polygon transaction status: success, failed, pending, dropped
The status line is the most important field, so it's worth knowing exactly what each value means.
| Status | What happened | What to do |
|---|---|---|
| Success | Included and executed | Nothing, it's done |
| Failed | Included but reverted, fee paid | Find the reason, retry |
| Pending | Waiting in the mempool | Wait or speed up |
| Dropped / not found | Removed from the mempool | Resend with correct nonce |
Success means the transaction was included in a block and executed without errors. Every transfer and state change it contained is now part of the chain.
Failed (PolygonScan says “Fail”, some wallets say “Reverted”) means the transaction was included in a block, but the contract stopped execution and rolled back all changes. Your tokens didn't move, yet the fee for the work done was still charged. That feels unfair, but validators did process it, and the fee is how the network prevents spam.
Pending means the transaction has been broadcast but not yet included in a block. On Polygon, with blocks every two seconds, a pending state that lasts more than a minute usually has one of two causes: a gas price below what validators currently accept, or an earlier transaction from the same address with a lower nonce that is itself stuck. Our Polygon mempool explorer shows the current queue and explains how to speed up or cancel.
Dropped isn't a status on the chain. It means nodes have discarded the pending transaction, usually because it sat too long with a low fee, or because you sent a replacement with the same nonce. Some explorers label this “Dropped” or “Dropped & Replaced”; others simply stop finding the hash. A dropped transaction never happened, so no fee was paid and no funds moved.
Why a Polygon transaction failed: out of gas and reverted
When you see Failed, scroll to the error message. PolygonScan shows it under the status, Blockscout shows a “revert reason” when the contract provides one. Two families of errors cover almost every case.
Out of gas means the gas limit was too low for the work the transaction needed. The tell-tale sign is gas used equal to 100% of the limit. This happens when a wallet's estimate is off, often during busy periods or with complex contracts, or when someone manually lowered the limit to “save” on fees. The fix is simply to retry with the wallet's default estimate or a slightly higher limit. Remember, you only pay for gas actually used, so a generous limit doesn't cost more on a successful transaction.
Execution reverted means the contract itself refused to continue. The code checked a condition and it wasn't met. Typical reasons: a swap's price moved beyond your slippage tolerance, the deadline passed, you didn't have enough allowance (you need to approve the token first), your balance was too small once fees were counted, or the contract is paused. The revert message, if present, often says it outright, such as “insufficient output amount” or “transfer amount exceeds balance”. For a deeper trace of complex failures, developer tools like Tenderly or Phalcon replay the call step by step; we compare them in our explorer alternatives overview.
Internal transactions and logs
Some of the most important information sits in tabs below the main fields.
Internal transactions are movements of POL triggered by a contract during execution, rather than signed directly by a wallet. If you sold tokens on a DEX for native POL, the POL you received arrives as an internal transaction from the router contract. That's why a wallet balance can go up with no incoming transaction in the main list; check the “Internal Txns” tab on PolygonScan or the internal transactions tab on Blockscout.
Logs, also called events, are records the contract writes as it runs. Every ERC-20 transfer emits a Transfer event with the sender, recipient and amount, and explorers build the token transfers section from these logs. If you ever doubt a token transfers summary, the raw logs are the ground truth. Developers use logs to confirm that a specific event, such as a mint or a deposit, really happened. Explorers that decode logs, like PolygonScan and Blockscout for verified contracts, save a lot of manual work.
Confirmations and finality on Polygon PoS
Confirmations are the number of blocks produced after the one that contains your transaction. More confirmations used to mean more safety, because a chain reorganisation could replace recent blocks. Polygon had a reputation for occasional reorgs in its early years, so exchanges asked for hundreds of confirmations.
That changed with the Heimdall v2 hard fork on 10 July 2025. Polygon PoS now has deterministic finality in about five seconds, so once a block is finalized it can't be replaced. Later upgrades aimed at reorg-free block production pushed in the same direction. In practice, a transaction with a handful of confirmations is final. Exchanges may still wait for their own internal number of blocks before crediting a deposit, which is a policy choice rather than a network limit.
Separately, Polygon PoS periodically writes checkpoints of its blocks to Ethereum. You don't need to wait for a checkpoint for a normal transfer, but withdrawals through the PoS bridge do, as explained on our bridge explorer page. You can watch checkpoints arrive on the Heimdall explorer, and read the technical background in the Polygon documentation.
Double-checking and sharing what you found
If a transaction matters, such as a large payment or a disputed transfer, open it on a second explorer. Our tool links every result to the same page on PolygonScan, Blockscout and OKLink, so you can compare in one click. When all three agree, you can be confident. You can also press Share to send a clean link or QR code to the other party; our payment verification guide explains how to use that as proof.
If the transaction was a withdrawal you funded from an exchange and you still need POL for future gas fees, a regulated exchange that holds licences in several jurisdictions and supports direct Polygon PoS withdrawals is the simplest source. Choose the Polygon network on the withdrawal screen, then check the hash here once it's sent. For the bigger picture of which explorer fits which job, see our ranking of Polygon explorers or head back to the guides hub.