LayerZero Scan Inflight Status: What Your Transfer Is Waiting For
LayerZero Scan inflight status meaning: the source transaction sent the message, but Berachain has not verified and executed it yet; see which stage is waiting.
By The Coin Wire Editorial4 min read

On LayerZero Scan, Inflight means the source transaction emitted a message, but it has not yet been verified and executed on Berachain.
- Source confirmations must accrue before verification can complete.
- Configured DVNs verify the message; an Executor delivers it on the destination.
- Payload Stored means destination execution failed and the stored message needs a retry.
What happens while a message is Inflight?
Inflight covers the time between a message being sent on the source chain and successful execution on the destination. The transfer begins when the source transaction emits the LayerZero message. The source chain then needs to reach the confirmation requirement configured for that app’s route.
After that, the route’s configured DVNs—Decentralized Verifier Networks—verify the message. Once verification meets the route’s security requirements, an Executor can commit and execute delivery on the destination chain. LayerZero describes these as distinct verification and delivery stages in its V2 protocol overview.
LayerZero Scan looks up messages by source transaction hash and shows statuses such as Inflight and Delivered. Open the source hash to inspect the message and, when available, the verification and Executor activity. The Berachain bridge covers transferring assets across chains for use in Berachain’s DeFi ecosystem, which is the route context for this pending message.
How to tell normal waiting from a delay
An Inflight message can be waiting at more than one point in the route. While source confirmations are still accruing, the message is waiting for the configured threshold. That is ordinary chain processing, even if the source transaction itself is already visible in its explorer.
Take an ETH transfer from Ethereum to Berachain. The Ethereum transaction emits the message, and the status stays Inflight while the required confirmations accrue. DVNs then verify it. When the Executor successfully executes it on Berachain, the status changes to Delivered and Scan shows a Berachain-side destination transaction hash.
If the source has passed its confirmation requirement but the status remains Inflight, the delay is further along the configured path: verification may still be pending, or the message may be awaiting destination execution. The required DVNs and timing depend on the app’s configuration, so there is no single waiting period that applies to every transfer.
Compare the source hash with the message details in Scan. Look for whether the confirmation stage appears complete and whether the configured DVNs or Executor show activity. A long wait after confirmations have accrued points to a verification or execution delay; Inflight alone does not identify which service is responsible. Keep the source hash and message details when contacting the bridge’s support channel, so they can trace the specific route.
Why Payload Stored needs a different response
Payload Stored means the message reached the destination endpoint, but destination execution reverted. It is a later, different condition than Inflight: delivery was attempted, but the destination app did not complete its execution.
The endpoint retains the verified payload so it can be retried. That makes the next step different from waiting for confirmations or sending a new transfer. Use the bridge or app’s retry process for the stored payload, following its instructions; a retry targets the existing message. Starting another transfer would create a separate message rather than resolve the stored one.
Delivered is the completed state in this flow: the Executor’s destination transaction executed successfully, and Scan records its Berachain-side hash. Payload Stored signals a failed execution that can be retried; Inflight signals that the message has not yet completed verification and execution. Those labels help distinguish a pending cross-chain message from one that has already reached the destination and needs recovery.
What to do next
For an Inflight transfer, open the source transaction hash in LayerZero Scan and identify whether source confirmations are still accruing or the configured verification and execution stages are pending. That tells you whether to keep waiting or raise a route-specific delay with the bridge operator. If the status is Payload Stored, follow the app’s stored-payload retry steps instead; this targets the existing message and shows whether the destination transfer can complete.