How to Check a Wormhole Transfer That Looks Stuck

To check a Wormhole transfer that looks stuck, find its source transaction and trace the message through to the destination chain. A transfer usually has several steps: the source transaction is confirmed, Guardians sign a message, and the destination app or wallet completes delivery. Knowing which step has paused tells you what to do next.

Start with the transaction hash from the wallet or app you used. Look it up on the source chain’s block explorer and confirm that it succeeded. Then search the hash in Wormhole Explorer to see whether the message has been observed and whether it has reached the destination. For a closer look at what can happen between those steps, see this guide to Wormhole bridge transfers and their integration details.

What should I check first?

Check the source transaction before retrying anything. If it failed or is still pending on the source chain, Wormhole cannot complete the transfer yet. If it succeeded, compare the source and destination chain, token, amount and recipient address shown in the transaction or transfer screen. A wrong destination address can leave funds somewhere you cannot access.

Keep the source hash handy; it is the key reference for tracking the transfer. A wallet’s activity list may show only the first transaction, while the Wormhole Explorer can show whether a message was created and what happened after that.

Why can a transfer pause after the source transaction?

A successful source transaction does not always mean the destination transfer is complete. Wormhole’s Guardians observe the source message and sign it. That signed proof is called a VAA, short for Verifiable Action Approval. The destination chain must then verify the proof and process the transfer.

Check which stage the tracker reports. If the source transaction has not reached the required confirmation level, wait for the chain to confirm it. If the message is waiting for a VAA, the signing step is unfinished. If the VAA is ready but the destination transaction is missing, the destination step may still need to be submitted.

What can I do if the destination step is missing?

Return to the app or route that started the transfer and look for a claim, redeem or complete action. Some routes handle delivery automatically; others require you to finish it. Use the same destination chain and recipient shown in the transfer details. If you need to contact the app’s support team, include the source hash and the status you see, but never share your seed phrase or private key.

• Source pending: wait for confirmation on the source chain.
• Message waiting: check again after the Guardians have had time to sign it.
• Ready to redeem: use the originating app’s completion step if one is shown.
• Destination transaction failed: inspect its error on the destination chain before trying again.

When should I stop waiting?

If the tracker does not change, first confirm the source transaction succeeded and that you are viewing the correct transfer. Then check the originating app’s status or support guidance: route rules differ, and some transfers can only be completed by the app that started them. The useful distinction is whether the message is still progressing or whether a destination action remains for you to take.