Track each leg of a wallet transfer on its own blockchain explorer. If you are used to an exchange, you may expect one status line; from your own wallet, a cross-chain move can leave separate records on separate networks. Knowing which record answers which question helps you tell “sent” from “received.”
- Find the transaction ID and check the sending network first.
- For a cross-chain move, track the destination as a separate leg.
- Check the final asset and address before treating it as complete.
Start with the sending network’s record
A block explorer is a public website that displays activity recorded on one blockchain. Open the explorer for the network your wallet sent from, then search using the transaction hash, a unique transaction ID shown in your wallet’s activity.
Check that the sender, recipient, asset, and amount match your transfer. Then read the status: “pending” means the network has not finished recording it, “failed” means the action did not complete, and a successful status means that transaction ran. A confirmation is a block added after the transaction; more confirmations can make its record harder to reverse.
Ethereum.org describes explorers as places to look up a transaction hash and status. On Solana, the transaction’s first signature serves as its identifier, as the Solana documentation explains. The labels differ, but in either case, copy the ID from the wallet rather than searching by amount alone.
Follow each leg when the destination is another chain
A cross-chain bridge moves value between blockchains, so one transfer may involve an outgoing transaction and a later incoming transaction. These are separate records: the source ID usually will not find the destination transaction in another network’s explorer.
For example, imagine you send an asset from Ethereum and want a different asset on Solana. First confirm the outgoing Ethereum transaction; then look for a destination-side record on Solana. A cross-chain bridge can create separate records, which is the basic idea behind what Biswap does across chains: a move and swap can be handled as one user task even though the blockchains keep their own records.
A successful source transaction proves that the first leg completed. It does not by itself prove that the destination asset arrived. If the destination record is not visible yet, allow time for the cross-chain process to finish and check again; do not treat the source status as proof of receipt.
Compare the record with what your wallet should receive
Once you find the destination transaction, check its status and recipient address. Confirm that the asset and amount are what you expected, allowing for any conversion or stated costs shown before you sent. A matching ticker alone is weak evidence: different tokens can share a name, so check the asset’s network and identity in your wallet.
There are two useful cases to keep apart. In a same-chain swap, one explorer may show the transaction that spends one asset and returns another; in a cross-chain transfer, the receiving asset belongs to a different network and needs its own record. That distinction is why Biswap users should verify both the source and destination when their move crosses chains.
Keep a simple trail if the record is unclear
Save the source transaction ID, network, destination address, and approximate send time. If the destination explorer shows no matching transaction, first make sure you selected the right network and copied the right address; searching the wrong explorer can look exactly like a missing transfer.
If the source shows a failure, the intended transfer did not complete on that chain. If the source succeeded but the destination is still absent, keep both details together and use the service’s stated help route. In your place, I would only count the move as finished after the destination record shows the expected asset at my address.