How to track a cBridge transfer after sending and what to do next
How to track a cBridge transfer: use the app history and source and destination explorers to confirm delivery, or see whether the transfer needs a refund.
Onchain Daily Newsroom4 min read

cBridge transfers are tracked in the app history and on the source and destination block explorers, so you can see whether the tokens arrived or the transfer needs attention. Use cBridge to follow the transfer; the Celer bridge validates transfers through the State Guardian Network before releasing assets on the destination chain.
Find the transfer in the cBridge app history
The app history ties the transfer’s current status to the wallet that sent it. Connect the same wallet you used to submit the transfer, open the transfer history, and locate the entry by its time and amount. You will need the sending wallet and, if available, the source transaction hash.
Matching both the wallet and the approximate time helps distinguish this transfer from other activity. An amount alone may not identify it if you have made several transfers. Open the matching entry and read its status before deciding what to do next.
A status is a view of the transfer’s progress, not a substitute for checking the chain records. The Celer bridge uses the State Guardian Network to validate a transfer before assets are released on the destination chain. That validation is why a transfer can be in progress after the source transaction has already been recorded.
Confirm the source transaction on its explorer
The source-chain explorer shows whether the deposit transaction was recorded on the chain where you sent the assets. Copy the source transaction hash from the transfer details or wallet activity, open the explorer for that source chain, and search by transaction hash. Etherscan and BscScan are examples of block explorers; use the one corresponding to the source chain.
Read the transaction record and confirm that it succeeded. A successful source transaction establishes that the assets were deposited for the bridge transfer. If the transaction is pending or failed on the source chain, the transfer has not reached the same point as one with a successful deposit, so use the app history status to understand its current state.
Keep the source hash distinct from any destination hash. Each completed transfer has a transaction hash on the source chain and another on the destination chain. They refer to separate on-chain records, and each belongs in the explorer for its own chain.
Use the destination hash to verify delivery
The destination-chain explorer confirms whether the bridge released the assets on the receiving chain. When the app history shows a destination transaction hash, copy it and search for it in the explorer for the destination chain. Confirm the transaction record, then check the destination wallet for the transferred tokens.
A completed transfer has both source-chain and destination-chain transaction hashes. The source record confirms the deposit; the destination record confirms the release. Seeing both records, along with the tokens in the destination wallet, is the clearest confirmation that the transfer finished.
When the app history has no destination hash yet, do not treat the source record alone as proof of delivery. The State Guardian Network validation and the destination-chain release are later parts of the process. Return to the history to see whether the status has changed, then check the destination explorer when a hash is available.
Request a refund when the status offers one
A refund status means the app offers a recovery path for the transfer, and you must request it in the app. A transfer can fail, including because of slippage, without being refunded automatically. Follow the refund action for that transfer and sign the resulting transaction on the source chain.
The refund transaction requires source-chain gas. Signing confirms the on-chain action that returns the tokens; the original source transaction by itself does not perform the refund. After requesting it, use the source-chain explorer to look up the refund transaction hash and verify that the transaction succeeded. Then confirm that the tokens have returned to the source wallet.
If the history does not offer a refund, do not assume that a failed or delayed transfer has one available. Read the current status and compare it with the source and destination records. The history identifies the transfer stage, while the explorers show what was recorded on each chain.
The transfer is finished when the tokens appear in the destination wallet, or when a requested refund lands back on the source chain. The app status shows which action is relevant, and the two chain records verify the outcome; together, they tell you whether to wait, confirm delivery, or recover the tokens.