How to Check a Bitcoin Wallet Address

Every bitcoin address is public. Anyone who has the string can look up its balance and every payment it has ever sent or received, without permission and without an account. That is not a leak — it is how the ledger was designed. This is a practical guide to reading it: how to check a bitcoin wallet address, how to find one specific transfer, what confirmations mean, and where the same habits apply to USDT on Tron.

What an address reveals, and what it does not

Paste an address into a block explorer and you get four things: the current balance, the total received and sent, a list of every transaction with amounts and timestamps, and the fees paid. All of it is history — you cannot change it, and neither can anyone else.

What you do not get is a name. The chain stores addresses, not people. There is no field for an owner, no registry to query, and no way to turn an address into an identity by looking at the ledger alone.

That distinction matters more than it first appears, and we come back to it at the end: anonymous is not the same as unlinked. An address carries no name, yet its transfers can still be tied to each other, and sometimes to you.

Looking up an address in an explorer

A block explorer is a website that reads the blockchain and renders it. You do not need to install anything, and you never enter a private key or a seed phrase — an explorer takes only the public address.

• mempool.space — the clearest view of what is happening right now: pending transactions, current fee levels, and how full each block is.
• blockchair.com — good for digging through history, with search across many chains at once.
• blockchain.com/explorer — the oldest of the three and the one most people land on first.

Paste the address into the search box. If nothing is found, the address has never been used: a freshly generated address exists only in your wallet until a payment reaches it, and until then no explorer in the world knows about it. An unused address is normal, not broken.

A wallet that shows nothing is not always empty. Check the address itself first — a typo returns a genuine "not found" rather than an error, because the explorer has no way to know the string was meant to be something else.

Finding one payment by its transaction ID

A balance answers "how much"; a transaction ID answers "did this particular payment go through". The ID — the TXID, or hash — is 64 characters of hexadecimal, and your wallet or the service you paid shows it as soon as the payment is broadcast.

Search the TXID instead of the address and the explorer shows that single transfer: which addresses paid in, which received, how much went where, the fee, and the number of confirmations.

Two details save most of the confusion here. A bitcoin transaction usually has several outputs, and one of them is normally change returning to the sender — so a payment of 0.01 BTC can appear as a transaction moving 0.4 BTC, and nothing is wrong. And the fee is paid by the sender, deducted from the inputs, never from the amount the recipient sees.

What confirmations actually mean

A transaction with zero confirmations has been broadcast but not yet included in a block. It sits in the mempool, waiting for a miner to pick it up, and how long that takes depends on the fee attached to it. Once it lands in a block it has one confirmation, and every block mined afterwards adds another. Blocks arrive roughly every ten minutes on average, though the spacing is random and half-hour gaps are unremarkable.

Six confirmations is the traditional threshold for treating a large payment as settled. Most services use fewer for small amounts, and the number is a policy choice rather than a rule of the protocol.

This is why sent is not the same as received. When an exchange says a deposit is pending, it usually means exactly this: the transaction is visible, it is real, and the service is waiting for its own confirmation threshold before acting.

Three address formats, one wallet

Bitcoin addresses come in several shapes, and the difference confuses people who assume a new format means a new wallet.

1. 1… — the original format, still valid everywhere.
2. 3… — introduced for multi-signature and later used to wrap SegWit.
3. bc1q… — native SegWit, defined in BIP-173, with lower fees.
4. bc1p… — Taproot, the newest of the four.

A modern wallet derives all of these from the same seed phrase, so they are the same wallet showing different faces. Each address still has to be looked up separately, because the chain has no notion of grouping them.

The formats also matter for a mistake that is expensive and common: sending coins to an address on the wrong network. The shapes overlap. Litecoin's older P2SH addresses begin with 3, exactly like bitcoin's, which is why Litecoin later moved to M — and why a 3… string alone does not tell you which chain it belongs to. Bitcoin sent to a Litecoin address is not bounced back; it is simply spent to an output nobody can claim.

We check for this where we can. When you create an order with us the destination address is validated against the format of the chain you picked, which catches a typo or an address pasted from the wrong network. It cannot catch a valid address that is merely the wrong one — no service can. And because an asset is chosen together with its network on our form rather than in a separate dropdown, there is no step at which the two can disagree.

USDT on Tron: the same lookup, a different guarantee

USDT on Tron — the TRC20 flavour most people use — is checked the same way, at tronscan.org. Tron addresses start with T and are 34 characters long. Paste the address or the TXID; you get balance, transfers, and confirmations, exactly as with bitcoin.

Two differences are worth knowing. Sending a TRC20 token costs network resources paid in TRX, so a wallet holding only USDT can receive fine and still be unable to send — the fix is a small amount of TRX, not a fix to the token.

The second is more fundamental. Bitcoin has no issuer. USDT does: Tether operates the contract and has, at the request of law enforcement, frozen balances at specific addresses. Whether that is reassuring or alarming depends on your position, but it is a real difference in what the asset guarantees, and no explorer will surface it for you.

When a transfer has not arrived

Start with the simple part: find the transaction by its ID. No ID and no record in the sending wallet means the payment was never broadcast at all.

From there the paths diverge. The transaction exists but sits at zero confirmations — that is almost always the fee, and it has a piece of its own: why a bitcoin transaction gets stuck and what to do. The confirmations are in but the coins are nowhere to be seen — the same piece covers those causes, from a receiving address you were not watching to a service's own crediting policy.

Two mistakes have no remedy at all, which is why they are worth checking first: a payment sent on the wrong chain, and one wrong character producing a valid-looking address that belongs to nobody. Compare the amount as well — services quote a specific figure for a reason, and a payment that arrives short is handled differently from one that never arrives.

What the chain shows about you

Return to where we started. An address carries no name — and yet, when a transaction spends several inputs at once, it is reasonable to assume they belong to one owner. Reuse an address across unrelated payments and those payments become linkable. Cash out at a service that knows your identity, and the identity attaches to everything upstream. This is the ordinary work of chain analysis, and it needs no special access: the data is public, which is the whole point of the design.

If you want to know how those links are scored in practice, that is a separate subject with its own tools — we went through the free ones here.

Monero takes the opposite approach: amounts and destination addresses are not published in the first place, so the lookups described above have nothing to read. The trade-off is real in both directions — you also cannot prove a payment to a third party by pointing at an explorer, which is why Monero has view keys for disclosing a transfer voluntarily. The project's own documentation explains the mechanism, and if you want to move between the two models, our bitcoin to Monero page carries the live rate and limits.

In short

• An explorer shows balance, every transfer, and confirmations for any address, with no account and no permission.
• It never shows a name — but linkage between addresses is ordinary analysis, not a special power.
• A TXID answers questions about one payment; change outputs make amounts look larger than they are.
• Zero confirmations means broadcast but not yet in a block; the number a service waits for is its own policy.
• 1…, 3…, bc1q… and bc1p… can all be one wallet — but a 3… string alone does not identify the chain.
• USDT on Tron checks the same way, needs TRX to send, and has an issuer who can freeze it.

Current rates for the pairs we support are on our rates page.