The source hash proves the send, while the destination receipt proves the other network completed its side, once the source transaction succeeds. These records can appear at different times because a bridge relays a message between chains. Checking both helps you avoid paying to send the same assets twice.
Each hash answers a different question
- Source transaction hash: Did the send happen?
- Destination transaction hash: Did the receiving network act?
- Receipt: Did that transaction succeed?
A transaction hash is a unique ID for one transaction on one network. It lets you look up that transaction in a block explorer, a site that displays network activity. A source hash alone does not prove the tokens arrived.
A receipt is the network’s record of a transaction’s result. On Ethereum, check that the source transaction succeeded; a failed transaction can still have a hash. A successful source transaction shows the send was processed, but the bridge’s message may still be waiting to complete.
The destination hash identifies a separate transaction on the receiving network, if the bridge creates one. Think of the source hash as a postage receipt and the destination receipt as proof of delivery. One does not replace the other.
Check the source before searching the destination
For Manta Bridge transfers between Ethereum and Manta Pacific, start with the source hash. Open it on the explorer for the network you sent from, then check its status, token, amount, and destination details. A hash viewed on the wrong network may look missing even when the send succeeded.
The official Manta Bridge is a way to move ETH or supported tokens between those networks. After confirming the source transaction succeeded, look for the bridge’s message status or destination transaction details. A pending message can explain why no destination receipt is available yet.
Timing depends on source confirmations and the bridge’s message processing. Confirmations are later blocks that make a transaction harder to reverse. If the source is successful but the destination is still pending, wait and check the same message again; sending a second transfer can create a duplicate.
If the destination hash appears, open it on the destination network’s explorer. Confirm the transaction succeeded and that the expected asset reached the intended address. For an ERC-20 token—a token using Ethereum’s common token standard—check its contract and amount too; matching names alone may not identify the same token.
Use the right check to save time and cost
Each network charges a gas fee, the cost of processing a transaction there. Rechecking a hash costs nothing, while submitting a new send can incur another source fee. With Manta Bridge, I’d retry only after the source failed or the transfer’s status indicates it did not complete.
Keep both hashes with the network names beside them. For a Manta Bridge transfer, that small habit makes repeated checks faster and helps separate a slow arrival from a failed send.
- Source hash: correct source network and successful status.
- Destination receipt: correct destination network and successful status.
- Asset: expected token and amount at the intended address.