How to Track a Wallet Transfer to Settlement

Track a cross-chain transfer through three checkpoints: source confirmation, message delivery, and destination settlement. A wallet transfer can pass the first checkpoint while the tokens are still unavailable on the destination chain.

Follow the message, not just the source transaction

Start with the transaction ID shown by your wallet and open it in the source chain’s explorer, a site that displays public transaction records. Check that it succeeded and that the app’s contract emitted a message, meaning a record asking another chain to act.

Then find the message ID or sequence number in the transaction details or the app’s tracker. This is the message’s own reference; it lets you follow the same action across chains. A source transaction marked “success” only confirms what happened on the source chain.

Think of two cases side by side: an exchange may show one “processing” status for your withdrawal, while a wallet transfer can show a successful source transaction and still be waiting for a signed proof or destination transaction. The proof is evidence that the source message passed the protocol’s checks. In omnichain apps, it helps coordinate actions across chains, but the destination contract must still accept and run the message.

For the broader steps behind how omnichain apps move assets, read the full explanation there; here, keep your attention on message tracking. For example, Wormhole uses a signed message called a VAA; other protocols, including Axelar and LayerZero, use their own message and tracking terms.

Confirm destination execution before counting the transfer

Settlement means the destination chain has completed the requested action, such as crediting tokens to your address. Look for a destination transaction ID and check its result in that chain’s explorer. A message marked “delivered” may still need a separate on-chain action before funds appear.

For example, if you send 100 tokens from Chain A to Chain B, record the source transaction and message ID. Follow that message until Chain B shows a successful transaction and your wallet balance reflects the credited amount. The tracker’s final status and the destination record should agree.

One edge case is a delayed destination transaction: the message may be verified, but execution can fail because the receiving app rejected it or needed more gas. Don’t resend while the original message is pending. Check its destination status and the app’s recovery guidance first; a second attempt could repeat an action if the first later completes.

Why does my source transaction say success, but my balance has not changed?

Source success means that chain accepted your transaction. It does not prove the message has been verified, delivered, or executed elsewhere. Use the message ID to check its current stage, then inspect the destination chain for a transaction. If no destination transaction exists, settlement has not yet been confirmed.

What should I save before closing my wallet?

Keep the source transaction ID, the message ID or sequence number, and the destination transaction ID once it appears. These identify each stage separately. If your wallet or app later shows only a general status, the IDs let you check the source and destination records directly.

When can I treat the transfer as complete?

Treat it as complete when the destination transaction succeeds and the expected tokens or app state appear on the destination chain. A signed proof or “delivered” label alone may not show that the final action ran. In practice, I check both the destination transaction result and the resulting balance.