How to Track a Cross-Chain Transfer's Arrival

You can estimate arrival by checking each chain’s confirmation and the bridge’s delivery status. A transfer may finish in seconds or take several minutes, depending on the chains, congestion, and the route used.

A transfer has two separate wait stages

First, the source chain must confirm your transaction. A blockchain is a shared record of transactions; confirmation means the network has accepted yours. A busy network or a bridge that waits for extra confirmations can make this stage longer.

Next, the bridge must complete the transfer on the destination chain. A bridge connects separate blockchains and carries instructions or assets between them. Its service may wait for source confirmations, then submit a new transaction on the destination.

That is why a source transaction marked “confirmed” does not always mean your funds have arrived. The bridge may still be processing the cross-chain message, or the destination transaction may need time to confirm.

Follow these steps to check progress

1. Save the source transaction ID. This is the unique code for your transaction. Copy it from the confirmation screen before closing the page.
2. Check it on the source chain’s explorer. An explorer is a website that shows blockchain activity. Search the transaction ID and check that its status says “success” or “confirmed,” not “pending” or “failed.”
3. Read the bridge’s status message. The bridge may show stages such as waiting for confirmations, processing, or completed. When learning how to bridge and swap with Mayan bridge, notice which screen provides the transfer status; keep that page open until it shows the next step.
4. Look up the destination transaction. If the bridge provides a second transaction ID, open it in the destination chain’s explorer. Check that it succeeded and that the receiving wallet address is yours.
5. Check the destination wallet’s token list. A successful transfer can deliver a different token from the one you sent. Confirm the token name and amount, and check that the wallet is set to the destination chain.

For example, say you send 1 token and the bridge quotes delivery of 0.98 of another token. The 0.02 difference may reflect fees or the exchange rate shown before you approve. Compare the quote with the amount received; do not expect the sent amount to appear unchanged when the route swaps tokens.

Know when a delay needs action

Wait while the bridge shows that it is processing, especially if the source transaction succeeded. Refreshing the page or starting a second transfer will not speed up the first one, and could make it harder to track both.

If the bridge says “completed” but the wallet looks empty, check the destination chain and token list first. Wallets may hide tokens until you add them, and some assets use a different token name after a swap.

If the source transaction failed, the bridge usually cannot complete that transfer. If the source succeeded but the bridge reports an error or remains stuck beyond its stated wait time, save both transaction IDs and contact the bridge’s official support. Never share your recovery phrase; support does not need it to investigate.

Track the source confirmation, bridge status, and destination receipt as separate steps. That sequence tells you where a transfer is waiting and what to check next.