Skip to main content
Hashbeam

Crypto protocols, markets and policy

2b8620

How to find the GnosisScan receipt after a bridge

How to find the destination transaction on GnosisScan after bridging: use Bridge Explorer to open the Gnosis receipt and verify the token arrival and recipient.

The Hashbeam Desk··4 min read

How to find the GnosisScan receipt after a bridge

Find the transfer in Bridge Explorer, then open its destination transaction on GnosisScan; each chain records its own execution, so the Ethereum hash identifies the source side. Have that source hash and the recipient address ready. omnibridge vs xdai bridge is a useful distinction when identifying which Gnosis Bridge route you used, since the asset and its destination evidence can differ.

Bridge Explorer connects the Ethereum hash to destination execution

Bridge Explorer accepts transaction hashes and addresses, so begin with the Ethereum transaction hash from the submitted transfer. It searches bridge records and shows the transaction details, including its direction and status. For a transfer from Ethereum, the direction should identify Mainnet to Gnosis.

The status helps explain what to do next. An initiated or collecting transfer is still in the bridge process; a completed transfer has been bridged successfully. If the record has not reached completion, return to it after processing advances. A source transaction can succeed on Ethereum before the corresponding Gnosis execution is ready.

  1. Search the source hash. Enter the Ethereum bridge transaction hash in Bridge Explorer’s transaction search. The visible result is a matching bridge record; if several records appear, use the recipient address and direction to identify the transfer.
  2. Open the matching record. Select the transfer and inspect its details and status. The visible result is the bridge record for the Ethereum-to-Gnosis movement, with its destination execution available when processing has completed.
  3. Follow the destination hash. Open the destination transaction linked from the matching transfer. GnosisScan displays the Gnosis transaction receipt, including the transaction outcome and transaction details. This hash is distinct from the Ethereum source hash because it records execution on the destination chain.

GnosisScan token transfers show ERC-20 arrival

For an ERC-20 transfer, verify arrival in the destination receipt’s token-transfer history. A bridge transaction can target a bridge contract while transferring tokens to the recipient: the transaction’s “To” address identifies the contract called, while the token-transfer record identifies the asset movement. These fields describe different parts of the same execution.

Match three values in the token-transfer record: the recipient address, the token contract, and the amount. The recipient should be the address expected to receive funds on Gnosis. The token contract identifies the asset on that chain, and the amount should match the bridged amount, accounting for any displayed token decimals. A matching record is evidence of the ERC-20 arrival even when the transaction itself is addressed to a bridge contract.

Say two transfers have the same sender, recipient, and amount. In the first, the destination asset is an ERC-20 token. Its Gnosis receipt can show the bridge-contract call and a token-transfer record naming the recipient, token contract, and amount. In the second, the destination asset is native xDAI. It is minted through block-reward accounting, so the balance can increase without a conventional incoming value transfer shown as a separate transaction to the recipient. The asset type changes the evidence to look for; the shared recipient and amount do not.

For native xDAI, inspect the bridge record’s destination execution and the GnosisScan block-reward accounting, including the receiver and amount in the mint event. Then compare the recipient’s balance history around that execution. The xDai Bridge’s documented flow records the receiver and amount with the block-reward contract, and the consensus engine updates the user’s xDAI balance. That explains why a native receipt may be confirmed by mint accounting and balance change rather than a normal incoming transaction.

Confirm the receipt or use the native balance evidence

The lookup is complete when the GnosisScan receipt matches the intended recipient and the ERC-20 token contract and amount, or when native xDAI mint accounting and balance history explain the arrival. If the bridge transfer is still processing, keep the source hash and recipient address and revisit its Bridge Explorer record after execution. Public GnosisScan receipts can be viewed without connecting a wallet; to share the result, copy and send the destination transaction URL.

Related

How to view GnosisScan without connecting a wallet?

Open the transaction URL in a browser. Public receipts are viewable without connecting a wallet.

How to share a GnosisScan transaction receipt?

Copy the destination transaction URL from GnosisScan and share it. The URL opens the receipt for the Gnosis execution.