Wormhole message tracking follows a transfer from its source-chain event through Guardian attestation to destination-chain execution. When an explorer lags, the reliable path is to identify the message from the confirmed source transaction, retrieve its VAA independently, and check the destination chain for redemption; an explorer status alone cannot prove where delivery stopped.
Identify the message from the source transaction
Start with the source transaction receipt and find the message published by the Wormhole Core Contract. On EVM chains, inspect the Core Contract’s LogMessagePublished event; on Solana, inspect the Core program’s emitted message and sequence data. The transaction hash is a useful search key, but the message identity is the tuple (emitter_chain, emitter_address, sequence).
Record the source chain ID, emitter address in Wormhole’s 32-byte format, sequence number, transaction hash, block or slot, and consistency level. A Token Bridge transfer can publish a message after locking native tokens or burning wrapped tokens; that event proves source-side initiation, not destination completion. Preserve the raw receipt or transaction data so you can recover the message identity even if an indexer has not yet indexed it.
For an Ethereum-to-Solana transfer, for example, the Ethereum receipt may show the Token Bridge’s Core message while Wormholescan still shows no transfer row. Extract the emitter and sequence from that receipt, then query for the VAA by those fields. This keeps your tracking tied to protocol identity instead of a search result that may appear late.
Separate source confirmation, attestation, and execution
These are distinct states, and each needs different evidence. Source confirmation means the chain accepted the transaction at the required consistency level; attestation means Guardians produced a VAA; execution means the destination contract accepted the VAA and completed the application action.
The VAA body carries the emitter chain, emitter address, sequence, consistency level, and payload. Guardians sign its hash after observing the message and reaching a two-thirds supermajority. A VAA can therefore exist before the destination transaction is submitted, and a destination transaction can fail even though the VAA is valid.
Wormhole’s VAA documentation describes lookup by the emitter tuple and warns that low consistency levels can create reorganization ambiguity. Treat a VAA as a protocol proof, not proof that assets reached the recipient. For completion, verify the destination transaction receipt and the Token Bridge redemption event or resulting token balance, as appropriate to the integration.
Recover when an explorer has stale message data
If the explorer has no message yet, query the source RPC directly and verify the transaction succeeded and emitted the expected Core event. Then request the VAA from an independent Guardian RPC or Wormholescan API using the emitter chain, emitter address, and sequence. Compare the returned VAA body against the source event before submitting it; for an EVM message, a mismatch in any identity field means you are tracking the wrong message.
When your case involves a wormhole bridge security review, verify that the VAA’s emitter is the expected Token Bridge contract and that the payload’s destination chain and recipient match the user’s intent. The VAA proves Guardian attestation of a message, while the destination contract still enforces its own verification and replay rules. For manual delivery, submit the signed VAA through the destination Token Bridge’s completion method; for automated delivery, inspect the provider’s execution status and destination transaction separately.
Use bounded polling rather than treating a slow indexer as a failed transfer: for example, poll every few seconds initially, then back off to a cap around 30 seconds, honoring any Retry-After response and retrying transient network or rate-limit errors. Keep a timeout for each state, emit metrics for source-confirmed-but-unattested and attested-but-unexecuted messages, and alert on age thresholds that fit the source chain’s finality and your relay service’s expected latency.
Handle reorgs, retries, and duplicate execution safely
A source transaction at a low consistency level can be reorganized after Guardians observe it. The same apparent emitter and sequence may then refer to competing observations, so do not permanently key a transfer only by sequence until the source block has reached the finality your application requires. For finalized messages, sequence-based replay protection is economical; for non-finalized flows, hash-based protection can distinguish VAA variants, but it does not remove the underlying reorg risk.
If a destination transaction reverts, check its revert reason and chain state before retrying. Common causes include insufficient destination gas, an invalid or already consumed VAA, a wrong recipient or chain ID, and a token not registered for that route. Query the destination contract’s consumed-message state or replay-protection record before resubmitting, since indexer lag can make an already completed transfer look pending.
Build a small state machine around on-chain evidence: source observed, source sufficiently confirmed, VAA available, destination submitted, and destination finalized. The Wormhole Core Contract reference documents the emitted sequence and consistency fields, while the Token Bridge transfer flow separates attestation from destination redemption. My practical rule is to retain the source receipt and message tuple, then reconcile every explorer status against RPC and contract state before presenting a transfer as complete.