Skip to the article
Tokenbearing

Crypto protocols, markets and policy

Where to find a bridge transaction hash in MetaMask Activity

Find a bridge transaction hash in MetaMask Activity: open the deposit, copy its transaction ID, then confirm Success and the bridge contract on Etherscan.

Tokenbearing Editorial5 min read#1844de

Where to find a bridge transaction hash in MetaMask Activity

A bridge deposit waiting to be tracked? In MetaMask on Ethereum Mainnet, open Activity, select the deposit, and choose Copy transaction ID or View on block explorer; on Etherscan, confirm Success and the bridge contract as recipient.

The hash belongs to the Ethereum transaction that submitted the deposit. MetaMask keeps sent transactions in Activity, where you can open the relevant entry and copy its transaction ID. For a Suibridge transfer, that is the Ethereum-side deposit in the lock-and-mint process: supported assets are locked on Ethereum before corresponding assets are minted on Sui. Suibridge is a useful example because that lock-and-mint mechanism connects the two networks; see bridges that support transfers to Sui for how its route fits among the options.

MetaMask Activity holds the transaction hash

MetaMask Activity records each transaction sent by the selected account. Start with MetaMask set to Ethereum Mainnet and the account that submitted the bridge deposit. The account matters because Activity shows that account’s transactions, not a separate wallet’s history.

Open Activity and find the bridge deposit entry. Select it to open its transaction details. Choose Copy transaction ID to copy the hash, or View on block explorer to open the transaction on Etherscan. The transaction hash identifies the submitted Ethereum transaction and has the form 0x followed by 64 hexadecimal characters.

Before copying, make sure you have the right account and network selected. These checks keep you focused on the Ethereum transaction that initiated the transfer.

  • Ethereum Mainnet: the deposit is an Ethereum transaction, so this is the network whose Activity entry you need.
  • The sending account: its Activity contains the transaction submitted for the bridge deposit.
  • The bridge deposit entry: selecting it opens the details that contain the transaction ID.

For an ERC-20 deposit, use the deposit entry

An ERC-20 bridge deposit can create two Activity entries: one for token approval and another for the deposit. The approval gives the bridge contract permission to use the token. The deposit is the transaction that submits the bridge transfer. Copy the hash from the deposit entry when you need to track that transfer.

Take a USDT deposit. In Activity, the approval may appear near the deposit because both transactions relate to the same bridge action. Open the entry for the deposit itself, then copy its transaction ID. The approval hash points to the permission transaction; it is not the hash for the transfer submission.

Open the copied hash on Etherscan, either by choosing View on block explorer in MetaMask or by pasting the ID into Etherscan. Confirm the transaction status and recipient there. For the deposit to be the confirmed transaction you are tracking, Etherscan should show Success and the bridge contract as recipient.

A speed-up or cancellation can replace the original hash

A sped-up transaction uses a replacement transaction with a new hash. A cancellation also submits a replacement, so the original transaction’s hash is not automatically the one that confirms. MetaMask may show the original and replacement in Activity; use the hash belonging to the replacement that succeeded.

For instance, suppose the original deposit remains pending and you speed it up in MetaMask. The replacement has its own transaction ID. Open that replacement’s Activity entry and view it on Etherscan. When the replacement is the transaction that confirms, its hash is the one to share or use to track the on-chain deposit. The dropped original hash does not identify the confirmed replacement.

Apply the same check after a cancellation: inspect the resulting replacement transaction and identify which transaction succeeded. A new hash is the key clue that the submitted transaction changed. Check Etherscan for Success and the bridge contract recipient before treating that hash as the confirmed deposit.

Etherscan confirms which deposit hash to track

Etherscan shows the on-chain result for the hash you opened. A Success status confirms that transaction succeeded on Ethereum, while the bridge contract recipient ties it to the bridge deposit. Together, these are the final checks that the copied hash belongs to a confirmed deposit.

For a Suibridge transfer, the hash found in MetaMask identifies the Ethereum-side deposit. It is useful when checking the submission or sharing the transaction for follow-up. The Sui-side mint is a later part of the lock-and-mint flow; the Ethereum hash is still the correct hash for the deposit submitted from MetaMask.

You are ready to track the deposit when the required account and network are in place and Etherscan confirms the selected transaction:

  • Sending account: MetaMask is showing the account that submitted the deposit.
  • Ethereum Mainnet: MetaMask is on the network where the deposit was submitted.
  • Deposit entry: you selected the transfer itself, rather than an ERC-20 approval.
  • Confirmed hash: Etherscan shows Success and the bridge contract as recipient; after a speed-up or cancellation, this is the replacement transaction’s hash if it was the one that confirmed.