Polygon Bridge transfers are trackable on-chain if you save the source hash and check both networks, whether bridging from Ethereum to Polygon PoS or back. To move supported tokens between those wallets, use the Polygon Bridge and keep the resulting hash. A withdrawal finishes only when its Ethereum claim confirms.
A transaction hash identifies one transaction on one blockchain. Search an Ethereum hash on Etherscan and a Polygon PoS hash on Polygonscan; each explorer shows whether that transaction succeeded, when it was included, and what token transfers it recorded. A successful source transaction proves that stage happened, but it does not by itself prove the tokens arrived on the other chain.
Think of the transfer as a parcel changing carriers. The first carrier’s delivery record shows that it handed over the parcel; you still need the second carrier’s record to confirm delivery. A bridge can likewise produce separate transactions with separate hashes, so do not expect to find the source hash on the destination explorer.
Start with the hash in your wallet’s activity history, such as MetaMask, and confirm you are looking at the transaction that moved tokens into the bridge. An ERC-20 approval is a separate transaction that gives a contract permission to use tokens. If the only confirmed hash is an approval, the transfer itself has not started.
For an Ethereum-to-Polygon deposit, first confirm the Ethereum transaction on Etherscan, then look for the mapped token arriving at your address on Polygonscan. Open the source transaction’s Token Transfers or event logs and check the token, amount, and bridge contract interaction. “Success” means Ethereum accepted the deposit transaction; Polygon still has to process the corresponding deposit.
For example, suppose you deposit an illustrative 100 units of a supported ERC-20 token. Your Ethereum balance falls when the tokens are locked in the bridge contract, and a corresponding token is credited on Polygon PoS. Search your receiving wallet address on Polygonscan, open its ERC-20 token transfers, and match the token and amount. The destination transaction may have a different sender and hash because the bridge completes that leg.
Check the token’s contract address as well as its ticker. The Ethereum token and its mapped Polygon token can have different contract addresses, while unrelated tokens can share a name or symbol. If Polygonscan shows the correct token transfer to your address but your wallet shows no balance, switch the wallet to Polygon PoS and check whether it displays that token.
A Polygon-to-Ethereum withdrawal has three stages to verify: the Polygon burn transaction, a checkpoint, and the Ethereum claim transaction. Search the withdrawal’s source hash on Polygonscan first. A successful burn removes the bridged tokens from Polygon, but it does not yet put the original tokens back in your Ethereum wallet.
A checkpoint records a batch of Polygon blocks on Ethereum so the bridge can prove that the burn happened. Once the burn is included, the withdrawal becomes eligible for an exit, also called a claim. The claim is another transaction you sign on Ethereum; search its new hash on Etherscan and check that it succeeded and released the token to your address.
This is the edge case that catches people coming from an exchange: the Polygon balance can be zero while the Ethereum balance is still unchanged. On the bridge back from Polygon to Ethereum, that combination can simply mean the burn succeeded and the claim remains to be made. Keep the burn hash; it identifies the withdrawal while you wait for the checkpoint.
Locate the last stage that actually succeeded before taking another action. If the source transaction is pending, check its status and gas settings in your wallet; if it failed, the bridge transfer did not begin, although gas spent on the failed transaction is still gone. If it succeeded, look on the destination chain or, for a withdrawal, check whether the checkpoint and Ethereum claim are still outstanding.
A Polygon Bridge status display can lag behind the blockchain if its transaction index has not caught up. Compare it with the relevant explorer’s transaction receipt and token-transfer records before assuming the funds are missing. A destination wallet that has not loaded the mapped token can also look empty even when its address has received it.
Keep one short record: source network and hash, destination address, token contract, amount, and any Ethereum claim hash. Use those details to distinguish a delayed deposit from an unclaimed withdrawal. Never enter a wallet recovery phrase to “release” a transfer; tracking needs public addresses and hashes, while claiming requires a normal transaction signed in your wallet.
An Ethereum-to-Polygon PoS deposit commonly takes roughly 10–30 minutes after the Ethereum transaction confirms, though congestion or processing delays can extend it. Watch for the Polygon token transfer rather than treating the Ethereum confirmation as the finish line. The source explorer’s timestamp gives you a useful starting point for measuring the wait.
A Polygon-to-Ethereum withdrawal often takes around one to a few hours because its burn must be included in a checkpoint before you can claim. The final Ethereum transaction then needs its own confirmation. These are planning ranges, not deadlines: a confirmed burn can remain unclaimed until you complete that last step.