A block explorer reveals two transaction hashes for a cross-chain transfer: one on the source chain and one on the destination chain. The first hash proves that a contract accepted your request; it does not prove that the recipient was paid.
Read the source transaction first
Start with the hash returned by your wallet, and verify the network before reading the fields. In an EVM explorer, check the status, block, confirmations, From, To, and token contract. A bridge deposit may show your address calling a router while the visible native-value field is zero. The actual ERC-20 movement is in the receipt’s Transfer logs: they identify the token contract, sender, recipient, and raw amount. If the status is failed or reverted, the bridge initiation did not complete, even if the wallet closed normally.
The next step is not to keep refreshing the same page. Find the destination transaction from the bridge’s status record or explorer link. A relayer, sequencer, validator set, or liquidity provider may need to observe the source event, wait for finality, and submit a separate destination call. If no destination hash exists, the transfer is still in that handoff; a successful source transaction alone is not evidence of delivery.
What the second hash can prove
On the destination chain, check the recipient and the asset contract again. Matching a ticker such as USDC or MANTA is not enough: representations with the same symbol can have different contract addresses, decimals, and issuers. Read the logs for the amount actually credited, then check internal calls or traces when the destination asset is native currency. This is where a fee, a different recipient, or a contract-side failure becomes visible.
That source-versus-destination check is the useful way to read a transfer on the Manta Bridge route.
The architecture is in the sequence
The two hashes also tell you what kind of route you used. A canonical bridge commonly locks or burns an asset on the source chain, carries a message or proof across, and releases or mints the destination representation. Its waiting time reflects the bridge’s finality and security assumptions. A liquidity route instead lets a provider pay from funds already held on the destination chain, then rebalance later; the destination transaction may therefore look like a pool payout rather than a mint. Meson Finance documents this pattern with liquidity providers, source-side bonding, destination-side locking and release, and a later source-side execution. Owlto Finance is another example where the app’s progress view should be checked against both chain explorers.
The explorer type matters too. Manta Atlantic is a Substrate parachain, so its record is organized around extrinsics and events rather than the EVM transaction fields you may know from Ethereum. Read the chain-specific record, then reconcile both sides: source action, destination action, recipient, asset contract, amount, and final status.