Check the destination chain before calling a bridge transfer complete

To confirm a bridge transfer, check the destination chain for the token arriving at your wallet address; a successful transaction on the source chain alone does not prove delivery. The source transaction starts the process, while the destination record shows whether the funds reached the other network.

What proves that a bridge transfer arrived?

The destination chain’s transaction record is the clearest evidence of receipt. Open that chain in a block explorer and search for your wallet address or the destination transaction hash shown by the bridge interface. Check that the record is successful and that the token transfer lists your address as the recipient.

A source-chain record can show that you approved a token, deposited it into a bridge contract or sent a message to another network. Those are steps in the transfer, not proof that the destination balance has changed. Some bridges process the destination step later, so compare the bridge’s status with the destination explorer before deciding that a transfer is stuck.

Route choice affects the process, including which bridge and token representation are involved. For the trade-offs behind choosing among routes, see this guide to comparing Polygon Bridge routes.

Which details should you match?

Match the destination network, wallet address, token and amount. A wallet can use the same address on several compatible networks, but its balance is separate on each one. Viewing the right address on the wrong network can make a completed transfer look missing.

Check these details against the bridge’s transfer record and your wallet:

• Network: Select the destination chain named in the transfer.
• Recipient: Compare the full destination address, not just its first and last characters.
• Token: Confirm the token contract or asset identifier. A bridged version may have a different contract from the asset on the source chain.
• Amount: Account for any fee shown by the bridge; the amount delivered may differ from the amount sent.

If the token does not appear in the wallet, check the explorer first. A wallet may not display a token automatically, even when the address holds it; adding the correct token contract can make the balance visible. Use the contract shown by a trusted bridge record or destination explorer, rather than a token name alone.

What should you do if the funds are not visible?

Start with the transfer status and transaction hash provided by the bridge. If the source transaction failed or remains pending, the destination step may not have started. If the source transaction succeeded, look for a separate destination transaction or status update; the bridge’s interface may identify whether the message is still being processed or needs another action.

Check the destination address and network again, then search the destination explorer directly. If it shows a successful transfer to the correct address but the wallet balance is absent, refresh the wallet or add the verified token contract. If the bridge reports completion but no matching destination record appears, keep the transaction hashes and contact the bridge’s support channel. Never share a recovery phrase or private key to investigate a transfer.

A transfer is confirmed when the destination chain records the expected token at the intended address. The next step depends on that record: wait for processing if no destination transaction exists, or investigate the wallet’s display if the explorer shows receipt. Until either status is clear, the cause of a missing balance remains unconfirmed.