Scan a Wallet and Get Details: A Practical Walkthrough
Scanning a wallet takes ten seconds. Reading the result correctly takes a little longer, and it is the part that decides whether the output is useful. This is the walkthrough: what to paste, what comes back, which fields to write down, and which to ignore.
The scan is the easy part. The skill is knowing which five numbers to write down before the page changes.
The Short Version
- Paste the address, pick the chain, and read four blocks: balance, activity, counterparties, flags.
- Record five details: address, chain, balance at scan time, transaction count, and the timestamp you looked.
- Ignore the headline balance as a trust signal. It is the least informative number on the page.
- A scan is a snapshot. Balances and histories change, so a screenshot without a date is weak evidence.
- If the result is going into a report, verify one number on a public explorer before you cite it.
Before You Paste Anything
Three checks, in this order, and they take under a minute.
One: is the address complete? Crypto addresses are long and unforgiving. A truncated paste, a missing character, or an accidental space will either fail validation or, worse, resolve to a different valid address. Copy from the source, never retype from a screenshot.
Two: is it the right chain? An EVM address is valid on Ethereum, BNB Chain, Polygon, Arbitrum and a dozen others. The same string can hold different balances on each. If you scan the wrong chain you will get a real answer to the wrong question, which is more dangerous than an error.
Three: is the tool asking for anything it should not? A read-only scan needs an address and nothing else. If a page asks you to connect a wallet, sign a message, or enter a seed phrase to show you a balance, close it.
What Comes Back, Block by Block
A scan result is usually four blocks. Read them in this order, because each one changes how you read the next.
| Block | What it shows | What to do with it |
|---|---|---|
| Identity | Address, chain, whether the account exists | Confirm the chain matches where the money actually moved |
| Balance | Native coin and token holdings right now | Record it with a timestamp. Do not read it as trust. |
| Activity | Transaction count, first and last seen, recent transfers | This is the informative block. Read the pattern, not the total. |
| Flags | Known-bad list matches, risk score, labels | Treat as a lead. Verify sanctions separately. |
Most people read the balance block and stop. The activity block is where the actual information is.
The Five Details Worth Writing Down
If you write down nothing else, write these. They are what a bank, a card issuer, or a police officer will ask for, and they are all things that change over time, which is why you record them now.
- The full address, exactly. Not shortened, not with an ellipsis. Copy it into a text file.
- The chain. "USDT" is not enough. USDT on Tron and USDT on Ethereum are different assets on different ledgers.
- Balance at the moment you scanned. With the date and time, including the timezone.
- Transaction count and first-seen date. Together these tell you whether the address is new, dormant, or active.
- The transaction hash that took your funds. If you are the victim, this is the single most important string in the whole exercise.
Five lines. That is a usable record. Everything else on the page is context.
Reading the Activity Block Properly
The transaction count is a number. The pattern behind it is the information. Four patterns cover most of what you will encounter.
| Pattern | What it looks like | What it usually is |
|---|---|---|
| Collection | Many senders, one recipient, funds accumulate | A fraud operation's deposit wallet |
| Relay | Funds in and out within minutes, balance near zero | Laundering hop designed to break the trail |
| Distribution | One sender, many fresh recipients | Payout wallet, or an exchange withdrawal batch |
| Dormant then active | Long gap, then sudden movement | An abandoned or seized wallet being emptied |
None of these is proof of anything on its own. A relay pattern is also what a payment processor looks like. The pattern tells you where to look next, not what to conclude.
Why the Snapshot Problem Matters
A scan is a photograph of a moving thing. The balance you see is the balance at the block the node had when you asked. Ten minutes later it may be different, and a month later the address may be empty because the funds moved on.
This has a practical consequence that catches people out: a screenshot of a wallet showing a large balance proves nothing about who owns it or whether the money is still there. Scammers exploit exactly this by showing victims a screenshot of a rich wallet as "proof" of an account. The wallet is real. The connection to the victim is fabricated.
So record the timestamp, and when you cite a balance, say when you read it. "Balance 12.4 ETH as of 2026-11-18 09:14 UTC" is a claim that can be checked against the block at that height. "Balance 12.4 ETH" is a claim that cannot.
Verify One Number Before You Cite It
Before any scan result goes into a report, a dispute, or a message to a bank, do this: take one number from the scan and check it on a public block explorer.
If the balance matches, the tool is reading the chain correctly and the rest of the output is probably sound. If it does not match, you have found either a stale cache or a bug, and you should not cite anything from that page.
This single habit separates a record that survives scrutiny from one that collapses the moment someone checks. It costs thirty seconds.
What to Do With the Result
Three paths, depending on what you found.
If the address is clean and you have not sent yet: you have done your due diligence. Keep the record. If the counterparty later turns out to be fraudulent, that record shows you checked.
If the address is flagged and you have not sent yet: stop. Do not send. A flag is not proof, but it is more than enough reason to walk away from a transaction you have not made.
If the money has already gone: the scan is now evidence. Save the address, the hash, the timestamp, and where the funds went next. Then report: your bank first if a card or transfer was involved, then the platform, then the relevant authority. The scan supports those reports; it does not replace them.
Reading the Counterparty List
The counterparty list is the most underused part of a scan result, and often the most revealing. It answers a question the balance cannot: who has this address been dealing with.
Three things to look for.
Concentration. If 90 percent of the inflows come from one address, this wallet is a downstream account of a single operation. If inflows come from hundreds of unrelated addresses, it is a collection point.
Known entities. A counterparty that is a published exchange hot wallet tells you the owner cashes out through that exchange. That is the single most useful fact in a trace, because it identifies who holds the records.
Fresh addresses. If most counterparties were created in the same week as the wallet itself, you are looking at a purpose-built cluster rather than an organic wallet. That pattern is common in fraud operations, which generate addresses in batches.
| Counterparty pattern | Reading |
|---|---|
| One dominant sender | Downstream account of a single operation |
| Hundreds of small senders | Collection wallet |
| Published exchange hot wallet | Owner cashes out there; that exchange holds records |
| All counterparties created the same week | Purpose-built cluster |
None of these is proof. All of them tell you where to look next, which is what a scan is for.
How to Take a Screenshot That Survives Scrutiny
Most people's evidence is a phone screenshot of a balance, cropped, with no date and no URL. It is worth almost nothing, and it is trivially dismissed.
Five things make a screenshot evidentiary:
- The full URL bar. It shows which explorer and which address, and it lets anyone reproduce the view.
- The block height or timestamp shown on the page. Anchors the claim in time.
- The whole page width. Cropping invites the question of what was cut out.
- The transaction hash, visible. The one string that is independently verifiable.
- A filename with the date.
2026-11-18_0914_eth-balance.pngsorts, and it dates itself.
Better still: save the explorer URL alongside the screenshot in a text file. A URL is smaller, permanent, and cannot be accused of being edited.
Questions people ask
What details can I get from a crypto wallet address?
Balance, transaction count, first and last activity, counterparties, token transfers, and any labels or flags a tool has attached. You cannot get a name, an address, an IP, or an email, because none of those are recorded on a public blockchain.
Is it safe to scan someone else's wallet address?
Yes. A public address is public by design, and reading it is not an intrusion. What carries risk is acting on a conclusion about a named person without evidence beyond the chain.
Why does a scanned wallet show zero balance but many transactions?
The funds moved on. A wallet that has been emptied still has its full history. This is common with relay addresses and with wallets that were used once and abandoned.
Can I scan a wallet without knowing which chain it is on?
Partly. The address format narrows it down, but an EVM address is valid on many chains. A good scanner will either ask you or try several chains and show you which ones have activity.
Does a wallet scan cost anything?
Reading public chain data is free. Some tools charge for exports, deeper history, or multi-chain reports. The scan itself should not cost anything.
What is the most important field in a wallet scan?
The transaction hash of the transfer that matters to you. Everything else is context. A hash is the one thing a third party can independently verify.
Should I scan my own wallet?
Yes, periodically. It shows you your own exposure: which addresses you have dealt with, whether any counterparty is now flagged, and whether your balance matches what you expect.
Check the address before you send anything
A free scan reads public chain data in your browser: balance, activity, counterparties and flags. No wallet connection, no seed phrase, no signup.
Primary sources and further reading
- mempool.space — Bitcoin explorer for verifying balances and hashes
- Etherscan — Ethereum explorer and source of record
- Tronscan — Tron explorer for USDT-TRC20 cases
- OFAC sanctions list search — authoritative sanctions screening
Related guides
Information only. We never promise recovery.