Check the destination chain, transaction receipt, and token contract. If you have moved assets across chains for the first time, a source-chain confirmation alone may not show that the destination wallet received anything. The key is to find evidence of the destination-side transaction and confirm it sent the intended token to your address.
What proves the token arrived?
A successful destination-chain transaction to your wallet is the clearest proof of arrival. A bridge may need to confirm the source transaction, pass a message or asset between networks, then complete a separate transaction on the destination chain.
That means the source transaction hash and the destination transaction hash can be different. The first proves your original transaction was recorded; the second can show whether the asset was delivered. An explorer can help you inspect those records, while Biswap is for moving and swapping crypto across chains in one flow. Those are different jobs: one helps you find evidence; the other performs the cross-chain move and swap.
For example, suppose you sent a token from one network to an address on Ethereum. The source explorer might show the send as confirmed, while Ethereum still has no destination transaction. That is evidence the first part completed, not proof that your Ethereum wallet has received the token.
What details should you gather first?
Before searching an explorer, write down the details that identify the transfer. A wrong network or address can make a successful transaction look like a missing balance.
- The source network and destination network.
- The sending transaction hash, a unique transaction identifier.
- The destination wallet address, copied from the wallet you meant to use.
- The token name and, if available, its contract address on the destination network.
- The approximate amount sent and the time you sent it.
A token contract address identifies a specific token on a specific network. The name and ticker alone are not enough: unrelated tokens can use the same name or ticker, and the same asset may have a different contract address on different chains.
How do you verify the destination transaction?
Use this sequence to move from the original send to a reliable balance check:
- Open the source transaction. Search the sending hash in an explorer for the source network. Confirm that the transaction succeeded and that the destination details match your intended transfer. A pending or failed source transaction cannot prove delivery.
- Check the transfer status. If the bridge or swap service provides a status reference, use the source hash to see whether the transfer is still being processed or has a destination transaction. A status marked complete is a clue; verify the destination record yourself when possible.
- Open the destination transaction. Check its hash on an explorer for the destination network. Confirm that the transaction succeeded, the recipient is your wallet address, and the token transfer matches the asset and amount you expected.
- Check the wallet on that network. Switch to the destination network and look at the asset list and balance. If the token is not listed, use the verified destination contract address to identify it in your wallet, if the wallet supports adding tokens.
- Compare the amount carefully. Token displays can use decimal places to convert the smallest units recorded on-chain into a readable balance. For example, a token with six decimals represents 1,250,000 smallest units as 1.25 tokens; the explorer may show either form.
If the transfer was made through Biswap, use the same evidence standard: look for a successful transaction on the destination network, then check its recipient and token details. The service name or a source-chain receipt by itself does not establish that the token is visible in the destination wallet.
Why might the wallet still show no balance?
A missing balance does not always mean the transfer failed. First check that the wallet is displaying the destination network and the same address that received the destination transaction.
If the destination transaction succeeded but the asset is absent from the wallet’s token list, the wallet may not display that token automatically. Verify the contract address on the destination network using a trustworthy source, then check whether your wallet lets you add or view that token. Do not add a token based only on a matching ticker.
If the explorer shows a failed destination transaction, the asset was not delivered by that transaction, even if the source send succeeded. If there is no destination transaction yet, the transfer may still be processing; the time can vary with network conditions and the bridge’s process. Avoid sending the same amount again just because the wallet balance has not updated.
Keep both transaction hashes and the destination details together if you need to ask the service that handled the transfer for help. They let you describe what happened without sharing your recovery phrase or private keys, which should never be needed to prove a transaction.
Use the destination transaction as your decision rule: if it succeeded to your address with the intended token, verify the wallet’s network and token display; if it is missing or failed, check the transfer status before taking another action.