Checking a Cross-Chain Transfer From Your Wallet

Checking a Cross-Chain Transfer From Your Wallet


When you bridge from your wallet, check the source transaction first, then confirm the destination receipt before treating the transfer as complete. Coming from a centralised exchange, you may expect one status to cover the whole move; on-chain, the source and destination are separate transactions. Knowing which one is pending helps you decide what to do next.

What does “pending” mean during a bridge?

A pending label can mean the wallet has not submitted your transaction, the source chain has not confirmed it, or the bridge route is still waiting to deliver funds on the destination chain. These are different stages, even if an app groups them under one label.

First, find the source transaction hash in your wallet’s activity or the bridge’s transfer details. Open it in the explorer for the source network and check whether it succeeded or failed; a hash from one network will not show the destination transaction. If the wallet only says “submitted” and shows no hash, check its activity before signing again.

Check the route’s network pair as well as its status: why Super Bridge uses native routes helps explain why a transfer between networks in the same ecosystem can settle differently from one crossing ecosystems. That context helps you interpret the route’s progress, while the explorers show what has actually happened on each network.

How do you confirm the destination received the tokens?

Once the source transaction succeeds, look for a destination transaction or delivery status in the bridge’s transfer details. The destination transaction usually has its own hash, so verify that hash in the destination network’s explorer and check that the recipient address is yours.

For example, say you send a token from Ethereum to Solana. The Ethereum explorer can confirm the source-side transaction, but it cannot prove that Solana has credited your wallet. You need the destination-side status too; the two transactions may have different hashes because they happen on separate networks.

If the destination explorer shows success but your wallet balance has not changed, check that you are viewing the correct network and token. Some wallets require you to add or select the token before showing its balance. Verify the token’s contract or mint address against the bridge’s transfer details; matching names alone is not enough.

What should you do if the two sides disagree?

If the source transaction failed, the transfer did not proceed through that source transaction; check the explorer for the failure reason before trying again. If it succeeded but the destination remains pending, avoid starting a second transfer: the first may still be processing, and a duplicate could send more funds.

Wait for the route’s stated processing window, then refresh the bridge status and destination explorer. Cross-chain delivery can take longer than a single-chain transfer because the route must observe the source transaction and complete the destination step. Super Bridge brings together routes from different providers, so timing and status details can depend on the route you selected.

If the wait has passed, gather the source hash, destination network, recipient address, token, amount, and any transfer ID shown by the service. Use those details to contact the bridge provider through its official support channel. Never share your seed phrase or approve a new transaction just to “release” funds.

How do you make the next transfer easier to check?

Before confirming, save the route details and note which address will receive the tokens. After signing, keep the source hash; once the route advances, record the destination hash too. If Super Bridge offers more than one route, compare its expected timing and fees alongside the quoted amount, since the fastest option may not be the cheapest.

I would wait for a successful destination receipt before spending or bridging the funds again. That gives you a clear end point: source succeeded, destination succeeded, and the expected token is visible in the correct wallet.

Can a source transaction succeed while the transfer is still pending?

Yes. Source success confirms that the source chain processed that transaction; the route may still need to deliver funds on the destination chain. Check the bridge’s route status and destination explorer before deciding that the transfer is complete or trying again.

Why is my destination balance unchanged after a successful transfer?

Check the destination network and recipient address first. Then confirm the destination transaction succeeded and that your wallet is displaying the correct token. A token may not appear by name until you add or select it, so verify its contract or mint address using the transfer details.

Should I retry if the bridge says pending?

Not while the original transfer may still be processing. Check the source hash, route status, and destination explorer, then wait for the route’s stated processing window. Retrying before you know what happened can create a second transfer instead of resolving the first.

Which transaction hash should I give support?

Start with the source hash and include the destination hash if one exists. Also provide the destination network, recipient address, token, amount, and any transfer ID shown by the service. These details help support trace both sides without requiring access to your wallet credentials.

Report Page