Skip to main content
Blockchain Today

Crypto markets, protocols and policy

How to Track a Transaction on LayerZero Scan from Send to Delivery

Track a transaction on LayerZero Scan by searching its source hash or sender address, then follow the message status and destination hash to delivery.

By Blockchain Today Editorial4 min read

How to Track a Transaction on LayerZero Scan from Send to Delivery

LayerZero Scan tracks a cross-chain transaction by linking its source transaction to a message status and, once delivered, a destination transaction hash.

Start with a transfer that has already been sent and the source transaction hash or sender’s wallet address. LayerZero Scan indexes messages sent through LayerZero endpoints, so one search can show the progress of a transfer across chains. This gives you a view of the message as a whole; a chain explorer shows transactions on its own chain.

  1. What should you search when you open LayerZero Scan?

    Open layerzeroscan.com and paste the source-chain transaction hash into the search box. Open the matching message to see its status and the chains involved.

    Lost the hash? Search for the sender’s wallet address instead. LayerZero Scan lists every LayerZero message that address sent across chains, which can help you find a transfer without retracing wallet activity one transaction at a time. For a transfer made through the Berachain bridge, keep the sending wallet address or source hash handy before you start; either gives you a way into the message record.

    An address search can return more than one message, especially when that wallet has sent transfers on multiple chains. Match the source chain and the transfer you recognize before opening a result. The address narrows the search to messages sent by that wallet, while the source hash points to one specific source transaction.

  2. How do you identify the right message?

    Read the source chain and source transaction hash on the message to confirm that the result matches the transfer you sent. The source hash is the transaction on the chain where the transfer began; it is not the hash for the transaction that may later execute on the destination chain.

    This distinction matters because a cross-chain transfer appears as a LayerZero message connecting activity on two chains. A search result can help locate the message, but checking its source chain and hash is the way to tie it back to the transaction you intended to follow.

    Once you have the matching message open, use its status as the next signal. The status describes where the message stands in the cross-chain process, while the hashes identify the on-chain transactions associated with it.

  3. What do Inflight, Delivered and Failed mean?

    Inflight means verification or delivery is still running. The message has not yet reached a completed delivery state, so return to its record later to see whether the status has changed.

    Delivered means the message executed on the destination chain. This is the status to look for when you want to confirm that the cross-chain transfer reached the stage of execution on its receiving chain.

    Failed means execution reverted on the destination chain. The status distinguishes that outcome from a message still in progress. This article’s task is to read the status and follow the hashes; the status itself tells you whether the message is still moving, executed, or reverted.

    These labels make the message view useful between the send and the destination transaction. A source-chain explorer can confirm the original transaction, but it does not present the LayerZero message’s cross-chain status in the same record. LayerZero Scan brings those pieces together for the transfer.

  4. How do you follow a delivered message to its destination?

    Read the destination chain and look for its transaction hash after the status changes to Delivered. Each message shows a source transaction hash, and once delivered it also shows a destination transaction hash. Click the destination hash to open that transaction in the destination chain’s explorer.

    For a Berachain bridge transfer sent from Ethereum, the source hash is on Ethereum. Once the message is delivered, its Berachain destination hash links to Berascan. The two hashes refer to separate chain transactions connected by the message, so use the destination hash when checking the receiving side.

    The final check is that the message says Delivered, names the destination chain you expected, and shows a destination hash that opens on that chain’s explorer. For the Ethereum-to-Berachain case, that means seeing the Ethereum source record and following the Berachain hash to Berascan. Together, the status and destination transaction show where the transfer went after it left its source chain.

  • Open layerzeroscan.com.
  • Search the source hash, or the sender address if the hash is lost.
  • Open the matching message and read its status and both chains.
  • When it says Delivered, open the destination hash in the destination explorer.