
How to Use a Block Explorer · Trace an On-Chain Transfer Step by Step
Most of what I turn over in this museum is old wreckage, but every one of those cases was reconstructed with the same instrument — a block explorer. There is nothing mystical about it and you do not need to write code: on most public chains, every transfer that reaches the chain is public and checkable, and a block explorer simply translates those raw records into a page you can read. This piece is not history; it is craft. I will take you from zero to checking whether a transfer arrived, reading every field on a transaction page, following the money one step further, and running a background check on an unfamiliar address before you send it anything. Once you can do this, a great many scams give themselves away before you press confirm.
(1) On most public chains, transfers that reach the chain are public, and a block explorer is the free web page that looks those records up — no registration, no code; (2) all you need is a transaction hash (TxID) or a wallet address to check whether money arrived, who it went to, and whether an address is clean; (3) what it gives you is evidence and leads, not a verdict — it can help you notice something wrong before you press confirm, but do not expect it to reach the conclusion for you. This piece teaches you to do all three.
I. Why this is the first tool you should learn
Start with a counterintuitive fact: on most public chains, every transfer you have already put on-chain is essentially permanently public and checkable by anybody (privacy chains, and the internal ledger movements at an exchange that never truly touch the chain, are the exceptions). That sounds like a privacy nightmare, but turned around it is the strongest self-defence instrument an ordinary person has — because every move a scammer makes is equally impossible to hide. The PlusToken mega-Ponzi was eventually traced transfer by transfer not through some hacking technique, but because people patiently walked address to address in a block explorer. You and I are using the same tool; most people have simply never opened it.
For everyday use, it solves at least three problems everybody runs into. One: confirming whether money actually arrived. A withdrawal from an exchange that has not landed after hours, a friend saying they sent it when you have not received it — do not sit and wait, and do not go hunting for so-called support; one lookup gives you the answer. Two: checking an address before you send. On-chain transfers are irreversible, and money sent to the wrong address is essentially unrecoverable, so glancing over an address's history in the explorer heads off plenty of elementary mistakes. Three: running a background check on an unfamiliar address or contract. When somebody pulls you into a project and asks you to send money to an address, check first whether that address was born yesterday or was flagged as fraudulent long ago.
Put differently, the block explorer is the starting point of every on-chain detective story in this museum. You do not have to become a detective, but learning to leaf through these public records will let you turn around at the entrance to a great many scams.
II. Three words first: hash, address, confirmations
There is no need to memorise jargon, but you do need to keep these three apart, or you will tie yourself in knots the moment you start.
Transaction hash (TxID) — the ID card of one specific transaction
Every on-chain transfer generates a unique identifier called the transaction hash, also called the TxID or transaction ID. It is usually a long 64-character hexadecimal string (chains such as Ethereum carry an 0x prefix, making 66 characters in total) and it looks like noise. What it corresponds to is one specific transfer — this one, unique. After you withdraw from an exchange or send from a wallet, you can almost always find it in the details of that record.
Address — the door number of an account
An address is the account that sends and receives, also a long string of characters. What it corresponds to is an account, not a single transaction. One address can have hundreds or thousands of movements underneath it. The mistake newcomers make most often is treating addresses and hashes as the same thing — remember: a hash looks up this one transfer, an address looks up every transfer for that account.
Confirmations — how many stamps this transaction has collected
Once a transfer has been packed into a block, every further block produced after it adds another layer of confirmation. The more confirmations, the lower the chance of the transaction being rolled back or overturned, and the more settled it is. A few confirmations are usually enough for small transfers; large amounts, or counterparties with stricter requirements, will wait for more. Watching the confirmation count climb in the explorer means the network is doing its normal work of vouching for that transaction.
III. Hands-on: check whether a transfer actually arrived
Now turn those words into actions. Say you withdrew some USDT from an exchange to your own wallet, waited a while, saw nothing, and want to know whether it is in transit or has landed. Do this:
- Step one: get the transaction hash. Go to wherever you initiated the transfer (the withdrawal history at the exchange, or your wallet's transaction history), find the entry, open the details, and copy the string labelled transaction hash / TxID / Transaction Hash. Exchanges will usually also give you a "view on block explorer" link directly — clicking that is easier still.
- Step two: find the explorer for that chain. This is the step people get wrong most often: different chains have their own explorers, and searching in the wrong place returns nothing at all. Whichever network you selected when withdrawing (ERC-20 goes to Ethereum, TRC-20 to TRON, BEP-20 to BNB Chain, and so on), use the explorer for that chain; and if you cannot keep them straight, the view link the exchange gave you will take you to the right place automatically.
- Step three: paste the hash and press enter. Paste the transaction hash into the search box at the top of the explorer, press enter, and the detail page for that transaction opens.
- Step four: look at the status first. The status field is the first thing to find on the page. Success means only that the transaction has been included and confirmed by the network — do not relax yet: success does not guarantee that the money reached the address you wanted, so continue to step five, check the receiving address, read the Token Transfers detail, and on chains that use a memo or tag (some exchange deposits, for example) check that the memo was carried correctly too, with enough confirmations behind it. Pending means it is still in transit; a busy network or a low fee slows it down, so refresh again later. Failed means the transfer did not execute and the money is usually still in your original account — do not keep firing off repeat transfers; work out why it failed, and note that on some chains the gas is deducted even when the transaction fails.
- Step five: check the amount and the receiving address. Confirm the amount sent, and that the address in the To field is character-for-character the address of your wallet. At that point you no longer need to ask anybody whether it arrived.
As long as you hold the transaction hash, you never need to hand a transfer over to any support agent or technician to check its progress for you — what they look at is the same public page you can look at. Anybody asking you to pay a fee to speed up a deposit or to unfreeze one is running a scam. The truth is laid out on the explorer, for free.
IV. What every field on the transaction page is saying
A transaction detail page looks alarmingly crowded the first time. In daily use you only need to recognise these:
- Status / Result: success, pending or failed, as above — always look at this first.
- From / To: which address the money left and which address it reached. These two lines are where you check an address. If To is a contract address, the explorer will usually attach a small Contract label, reminding you that this was not a transfer to a person but an interaction with a program.
- Value / Amount: how much of the native coin (ETH, TRX, BNB and so on) this transaction moved.
- Transaction Fee / Gas: what you paid the network for this transaction, which is a separate thing from the transfer amount and goes to miners or validators, not to the recipient.
- Token Transfers: this one is critical. If what you sent was a token such as USDT or USDC, the native-amount field will often read 0, and the real token movement is recorded under Token Transfers — which token, how much, from which address to which address. When checking whether USDT arrived, this is the field you read. Do not let the 0 above it alarm you.
- Block / Confirmations: which block this was packed into, and how many further confirmations have stacked up behind it.
- Timestamp: when this happened.
Get comfortable with those and you can read the overwhelming majority of ordinary transfers; the remaining technical fields do not come up in daily use, so leave them for now.
V. Going further: follow the money one step down
Once you can read a single transaction, take one small step forward: follow the addresses down. This is exactly what an on-chain detective does — click into an address, look at all of its movements, open the counterparty address of one of them, see where that address sent the money next, link by link.
Concretely: paste an address into the search box (an address, not a hash) and what opens is that account's overview page — its balance and a list of transactions ordered by time. Click the counterparty address of any entry in the list and you have stepped into the next account; keep clicking and you have drawn the escape route of a sum of money across the chain. Tracing the PlusToken proceeds and tracing stolen funds at the time used exactly this plainest of methods, only at greater scale and paired with address-clustering analysis.
For your daily life this move has two practical uses. One: if you are ever defrauded or send to the wrong address, you can see with your own eyes where the money went (seeing is not the same as recovering, more on that below). Two: verifying whether a claim is true — when a platform says its funds are all safely in cold storage, for instance, the larger venues publish reserve addresses so you can check them on-chain yourself, and where nothing can be found, or no self-verifiable evidence is offered, credibility should take a hit. This habit of checking on-chain yourself is covered in more detail in how to tell whether an exchange is trustworthy and in what proof of reserves means.
VI. Running a background check on an unfamiliar address
This is where a block explorer most earns its keep as prevention. Before somebody has you send money to an address, or has you interact with a contract, spend two minutes running a background check on it and a lot of holes open up in plain view. Look at a few things:
- Age and activity. Paste the address in and look at when its first transaction was. An address created yesterday that is in a hurry for your money is a warning sign in itself — a legitimate project's address usually has a checkable history behind it.
- The pattern of movements. Read the transaction list: does it only receive and never send, funnelling many people's money into one place? Is the same sequence of actions repeated against a large number of addresses? Those patterns are typical of collection wallets and batch harvesting.
- Public labels. Many explorers attach public labels to well-known addresses (certain known exchange hot wallets, for example) and also mark addresses reported by the community or confirmed as fraud or phishing. If the address is wearing a risk label, do not hesitate — turn around.
- If the counterparty is a contract. Be especially careful when To carries a contract label and you are being asked to confirm an approval. What a malicious contract usually wants is not a direct transfer but a signed approval, after which it drains your wallet at leisure. I take that family of signature-phishing and permission-rewriting plays apart in detail in the piece on the TRON multisig scam, which is worth reading alongside this one.
A clean background check does not mean it is definitely safe; but a background check that turns up something clearly wrong almost always means there is a problem. Its value is in trading a feeling for evidence.
VII. Honest limits: what it can and cannot do
Let me state the whole of it, so you do not expect too much. A block explorer can show you: whether a transaction arrived, whether the amount and addresses are right, an address's entire public history, how money moved across the chain, and whether any public risk label has been attached. These are hard facts, free, and beholden to nobody.
But there are three things it cannot do, and you should hold them clearly. First, it cannot prove who is behind an address. The chain holds addresses, not names; you can see which address the money went to, but the explorer will not tell you who owns it or what they intended. Second, being able to see it is not being able to get it back. After a fraud or a mistaken transfer you can watch the money leave in perfect clarity, but on-chain transfers are irreversible, and real recovery usually depends on an exchange's risk team freezing funds, on a police report, or on professional intervention — an individual armed only with an explorer can do essentially nothing. Third, it cannot protect you from being talked into it. However good you are at reading data, it will not stop somebody using a fake support agent or a fake prize to walk you into pressing confirm yourself. The tool governs evidence; it does not govern the human moment.
So put it back in its proper place: a block explorer is a background-check instrument for use before you decide, a lamp that keeps you out of a few pits. It is not a safe, and it is not magic for recovering lost assets. Real safety still comes down to building the habit of looking things up before you send or sign — and handing the risks you should not be carrying to somewhere better suited to carry them.
Learning to use a block explorer is one of the fundamentals of walking the self-custody road steadily — it lets you verify and diagnose on your own. But the flip side is that you will notice how much there is to guard against: identifying the chain, the address, the contract, guarding against signature phishing. Every link is yours to carry. That is exactly the cost of self-custody: you are your own bank, and safety rests entirely on you not making a mistake.
If you will admit that you are not yet confident of checking correctly every time and never being taken in, then holding the everyday, short-horizon part of your assets in custody at a large, transparent, self-verifiable venue does remove that whole class of risk — wrong chain, wrong address, wrong approval — because the on-chain step is no longer performed by your own hand. The cost is that you have to trust that venue, which is why the earlier files spend so long teaching you how to choose one. In practical terms, the least effortful starting point is a venue that lays out its own evidence: Binance has published self-verifiable proof of reserves monthly since November 2022, operates the SAFU user protection fund, and is licensed in several jurisdictions. That does not make it risk-free; it means its risk signals are far fewer than those of a small venue you cannot look up at all. Whether to register is your own decision, and for large long-term holdings, remember to move them to a wallet whose keys you hold yourself.
- Binance Academy, "What Is a Blockchain Explorer?" — the basics of what a block explorer is and what it can show. academy.binance.com
- Etherscan official help centre, Understanding an Ethereum Transaction — the meaning of each field, the status and the confirmation count.
- TronScan field documentation: how to read a TRX / TRC-20 USDT transfer (the Owner Address and Token Transfer sections).
- From this archive: the on-chain tracing records cited in PlusToken, a worked example of the method described here.
If you spot a factual error in this piece, please write to [email protected] — I will issue a public correction and credit you by name. The full correction history lives at /corrections.html. Editorial standards are at /editorial.html.