Futures
Access hundreds of perpetual contracts
TradFi
Gold
One platform for global traditional assets
Options
Hot
Trade European-style vanilla options
Unified Account
Maximize your capital efficiency
Demo Trading
Introduction to Futures Trading
Learn the basics of futures trading
Futures Events
Join events to earn rewards
Demo Trading
Use virtual funds to practice risk-free trading
Launch
CandyDrop
Collect candies to earn airdrops
Launchpool
Quick staking, earn potential new tokens
HODLer Airdrop
Hold GT and get massive airdrops for free
Pre-IPOs
Unlock full access to global stock IPOs
Alpha Points
Trade on-chain assets and earn airdrops
Futures Points
Earn futures points and claim airdrop rewards
Transfer "not received"? Step-by-step guide to using a blockchain explorer to find out the truth
Summary: Wallets are just the front-end entry point; the blockchain explorer is the only “evidence database.”
In Web3, many people’s first tense moment isn’t because the coins they bought suddenly dropped in value, but because after completing a transfer, exchange, or cross-chain operation, they find their assets haven’t appeared yet, and the other party says they haven’t received it.
At this point, the most common reaction from beginners is to refresh the wallet, log out and log back in, take screenshots and ask in groups, or even suspect that the wallet has a bug. But actually, the wallet interface is just an entry point; it shows the result, not the underlying facts. The place that records everything is the blockchain explorer.
This article will demonstrate using the SafePal wallet, through a real case of transferring 100 USDT (BEP20), to teach you step-by-step how to verify transactions using a blockchain explorer from scratch.
First step, find the TXID of this transaction
Every on-chain operation (transfer / swap / cross-chain) has an ID: TXID (Transaction Hash). You can think of it as the “unique number” for this transaction. As long as the transaction has been submitted to the chain, it can be looked up with this number.
Taking SafePal App as an example, after transferring 100 USDT (BEP20), you open the corresponding USDT token in the SafePal App, click on this transaction, and then in the details page, you will see the TXID (Transaction Hash).
Second step, choose the correct blockchain explorer
Assets on Web3 are not interoperable across different public chains. Before checking, first see which chain you transferred on. Here are the links to the blockchain explorers for the top 10 mainstream public chains according to CoinMarketCap rankings:
BNB Chain (BEP20): BscScan
Ethereum (ERC20): Etherscan
Tron (TRC20): TRONSCAN
Bitcoin (BTC): Blockstream Explorer
Solana (SOL): Solscan
XRP: XRPSCAN
Cardano (ADA): Cardanoscan
Avalanche (AVAX): Snowtrace
TON: Tonviewer
Polkadot (DOT): Subscan
For example, the USD/RMB/EUR/CHF in SafePal’s built-in bank account are RWA tokens issued by Fiat24 on the Arbitrum network, so your Fiat24 account balance and transactions can also be viewed on Arbiscan, fully transparent.
Using the previous example of transferring 100 USDT (BEP20), if you want to trace this transfer on-chain, the correct step is: open BscScan, paste the copied TXID, and search for this 100 USDT transaction. You will see the detailed record of this transaction:
Third step, understand the on-chain transaction status (Status)
When you enter the page, first look at the Status field:
Success: Indicates that from the chain’s perspective, this transaction has been completed.
Pending: Indicates that the transaction has been sent but not yet officially confirmed. Usually due to network congestion or low gas fees.
Failed: Indicates that this transfer did not execute successfully as expected. Assets are usually returned to the original address, but the fee has been deducted.
Search not found: Indicates that the transaction was never on the chain. Check the network and resend the transfer.
Fourth step, confirm the fund flow (Token Transfers)
A status showing Success does not necessarily mean you transferred correctly. Please verify the following three items:
From: Is this your wallet address?
To: Is this the correct address given to you?
Tokens Transferred: Does the token name and amount shown match what you sent out?
Pitfall avoidance: Many “not received” cases are actually due to wrong addresses or selecting the wrong chain.
Advanced tip: directly view the “full ledger” of an address
If you don’t have the TXID or want to see all assets and transaction records in your wallet address, searching the address directly is the fastest method.
Paste your wallet address into the browser’s search box, and you can see:
Balance: The native token (like BNB) balance of this address.
Token Holdings: Click here to see the real-time balances of all tokens (like USDT, various assets) under this address.
Transactions: This list records all historical transactions of this address. Clicking any Transaction Hash in the list will jump back to the transaction details page.
Fifth step, on-chain success but wallet not yet showing?
Using the same 100 USDT example, if BscScan clearly shows the transaction as Success, and Token Transfers also states that 100 USDT has arrived at the other address, but your wallet still hasn’t reflected it, the most common reasons are:
Display delay: Try pulling down to refresh, or switch nodes. If using the SafePal App, you can also clear the cache in the app’s settings on the top left of the home page and then check again.
Wrong network: Is the other party looking for BSC tokens on the Ethereum network? Different chains are different versions. You transferred BEP20 (BSC network USDT), but if the other person is searching on the ETH network for ERC20 USDT, they might think the assets haven’t arrived.
Token not added: Has the other wallet manually added the token contract address? If they also use SafePal, ask them to go to SafePal App → Coin (bottom) → Manage Tokens, search for and select the corresponding USDT, then refresh the asset page.
So, after confirming on the explorer that the 100 USDT has entered the other address, what you need to do is: remind the other party to switch to the correct network, confirm they have added the correct token, and then refresh the balance.
Conclusion
What this case truly aims to teach you is not just how to check a transaction, but to develop a troubleshooting sequence: find hash → choose the right chain → check status → verify address, or directly search the address to view the full ledger.
Learning to clarify the facts along a transfer and mastering blockchain explorers is the first step toward building on-chain thinking.