Why a confirmed cross-chain transfer can still be stuck

2 steps make up a typical cross-chain transfer: a transaction on the source chain and delivery on the destination chain. A confirmation proves the first step was recorded; it does not prove the second has happened.

That difference tells you where to look: check the transfer’s destination status, not just the source transaction.

Why does a transfer confirm before the funds arrive?

Each blockchain keeps its own record, so the destination chain cannot simply read a balance change from the source. A bridge or cross-chain service must verify the source event, then send a message or arrange a transaction that releases, mints, or swaps the asset on the destination.

Those steps may depend on block finality, bridge validators, or a relayer: software that forwards the verified message. The service may wait for more source-chain confirmations before acting, or its destination transaction may be delayed by network congestion. A confirmed source transaction can therefore be valid while the transfer is still in progress.

For a concrete example, a mantle bridge transfer has its own route and status checks; the fuller walkthrough explains how to follow it from send to arrival. The general rule is the same across bridges: confirmation on one chain is evidence of one stage, not proof of completion.

How can you tell which step is delayed?

Start with the transaction hash and open it in the explorer for the source network. Check that it succeeded, that the token and amount match what you sent, and that the destination address is correct. Then use the bridge’s official status page or transfer history, if available, to see whether it has detected the source event and submitted the destination transaction.

• Source transaction is pending: the source network has not included it yet. Check the wallet’s fee or replacement options.
• Source transaction failed: the bridge action did not complete. Read the explorer’s error details before trying again.
• Source succeeded, destination transaction is absent: the transfer may still be waiting for verification, finality, or relaying.
• Destination transaction succeeded: check the destination network and token contract in your wallet; the asset may not appear in the default token list.

Use the transaction hash from the bridge record to verify any destination transaction independently. A wallet display can lag or hide an unfamiliar token, but an explorer can show whether the destination address received it.

What should you do while it is pending?

Compare the status with the bridge’s stated processing steps, then give it time if it is waiting for confirmations or a relay. Different routes have different finality and processing requirements, so a delay on one bridge does not establish that another route will be faster.

Do not submit the same transfer again just because the destination balance has not changed. First confirm whether the original transfer is still processing, failed, or completed on the destination. If the bridge reports an error or the status remains unchanged beyond its expected process, contact its support through the official site and provide the transaction hash—never your seed phrase or private key.