Check Both Chains to Confirm a Polygon Bridge Transfer

2 chains are involved in a bridge transfer, so a successful transaction on the first chain does not prove the tokens arrived on the second. To confirm delivery, check the bridge’s status and look for the destination transaction or token balance in the wallet you specified.

That distinction matters because a bridge coordinates separate transactions across networks. The source transaction locks, burns or otherwise sends the asset into the bridge process; a later step makes the corresponding asset available on the destination chain. For a fuller explanation of how Polygon Bridge moves tokens between wallets, see our guide to the transfer mechanics.

Where can you check a Polygon bridge transfer?

Start with the bridge interface you used, then verify the relevant transaction on the source and destination chain explorers. Polygon Portal has a Transactions section for reviewing bridge activity, while other bridge providers show status in their own transaction history.

Find the transfer by its source transaction hash, wallet address, or transaction history entry. A transaction hash is the unique identifier for an on-chain transaction. Open the source-chain explorer link and confirm that the transaction succeeded and matches the asset, amount, and destination address you expected.

Then look for a destination transaction or a completed status in the bridge interface. If the source transaction succeeded but the bridge still says pending, the source step may be recorded while the destination step is still processing. The source explorer alone cannot confirm that the transfer finished.

What does a successful destination transaction look like?

A successful destination transaction should appear on the destination chain’s explorer, with the expected receiving address and token transfer. Check that the address is the one you entered in the bridge, especially if it differs from the wallet that sent the funds.

Inspect the transaction details for the token and amount. The asset may have a different representation on the destination network, so compare the token contract address or the bridge’s asset details when names or symbols look alike. A matching ticker alone is not enough to identify a token.

Also check the transaction status, not just whether a hash exists. A pending transaction has not finished executing. A failed transaction can still have a hash, but it does not mean the destination received the tokens. If the bridge shows a destination hash, open it in the explorer for that chain and check its result.

Why might the tokens not show in your wallet?

A wallet can be connected to the wrong network or address, or it may not display a token automatically. First switch the wallet to the destination network and make sure you are viewing the same receiving address used in the bridge.

If the destination transaction succeeded but the balance is not visible, check the token’s contract address against the bridge details or a trusted destination-chain explorer. You may need to add the token to your wallet’s display; this changes what the wallet shows, not the on-chain balance. Do not add a token based only on a familiar name or symbol.

A bridge transfer can also take time between its source and destination steps. The wait depends on the bridge route and the networks involved, so one fixed estimate does not apply to every transfer. Use the provider’s status and transaction links to see which step is pending before deciding that the transfer is missing.

What should you do if the transfer is still pending?

Use the source hash to trace the transfer, and follow the bridge’s own instructions if it offers a way to resume or complete a pending step. Avoid submitting a second transfer just because the first has not appeared yet; that can create a separate transaction without resolving the original one.

1. Open the bridge’s transaction history and select the relevant transfer.
2. Confirm the source transaction succeeded on its chain’s explorer.
3. Check the bridge status and open any destination transaction on the correct chain’s explorer.
4. If the status remains unclear, contact the bridge provider through its official support channel and share the transaction hash, never your recovery phrase or private key.

For most readers, the destination explorer is the clearest final check: it shows whether the receiving transaction executed and which address received the token. Treat the transfer as complete when the destination-side transaction succeeded and the token is associated with the intended address.