How to Read a Bridge Transfer in Three Explorer Checks

A bridge transfer is read through three explorer checks—source lock, destination issuance and final recipient—and Wormhole’s 120,000-wETH incident shows why all three matter. Wormhole’s incident report records an uncollateralized mint in one Solana transaction on February 2, 2022; a normal deposit would add one unit of backing for every wrapped unit issued, but this mint added none. Of the 120,000 wETH created, 93,750 was bridged back to Ethereum. That 78% conversion ratio, combined with a 100% backing deficit on the new issuance, made it a solvency event rather than an ordinary whale transfer. It still did not, by itself, prove a market sale.

What did the source-chain transaction actually do?

The first check is whether the source transaction locked tokens, burned them, merely approved a contract or moved funds between bridge-controlled addresses. Start with status, signer, destination contract and decoded method, then inspect token transfers and event logs. A “Success” label proves execution, not the interpretation attached to it.

The top-level value can also be misleading. ERC-20 deposits often show zero native value because the token movement appears in transfer logs, while internal transfers record native assets forwarded during contract execution. An approval moves no tokens at all; it only sets an allowance for a later call. The distinction is visible in Manta Pacific’s ERC-20 deposit sequence, where approval and deposit are separate transactions.

Did matching value arrive on the destination chain?

The second check is to match the source event with a destination mint, unlock or liquidity-pool payout of the same economic value. Canonical lock-and-mint bridges escrow the original asset and issue its mapped representation. Other bridges use inventory on both chains, so the destination payment may come from a liquidity provider rather than a mint.

• Match the token contracts, amount, recipient and bridge message identifier.
• Account for fees instead of demanding identical raw amounts.
• Check whether supply rose, escrow rose or bridge inventory fell.
• Treat unmatched issuance as a backing warning, not fresh capital.

A successful destination mint can remain idle in the recipient wallet. It is cross-chain deployment, but it has not reached a trading venue and should not be counted as immediate buy or sell pressure.

Where did the bridged funds go next?

The third check is to follow the destination asset until it stops at a wallet, lending market, DEX router or labeled exchange address. A transfer into another address controlled by the same bridge or owner is internal repositioning. An exchange deposit creates potential supply, while a swap event or pool balance change provides stronger evidence of execution.

Size becomes meaningful only against available liquidity. A hypothetical $10 million transfer arriving beside $200 million of relevant-side pool reserves equals 5% of that depth; the same transfer sitting unused in a wallet has no direct execution impact. For centralized venues, compare the amount with recent net deposits rather than visible wallet balances.

The verdict for traders is simple: over the next 24 to 72 hours, a bridge alert matters only if destination funds approach usable liquidity and then enter a venue. That view is invalidated if the recipient remains idle, routes the assets into collateral or custody, or sends them back across the bridge without a swap. Until the third check confirms venue exposure, the transfer is accounting—not a trade.