What a block explorer learns about you

Two separate privacy problems

People conflate these constantly and they have almost nothing in common.

The first is chain analysis: what can be inferred from the public ledger itself. This is the domain of clustering heuristics, transaction graph analysis and platforms such as Arkham. It affects everyone equally, it works retroactively, and it has essentially nothing to do with which explorer you use. The data is public and always will be.

The second is lookup privacy: what the operator of the website you used learns about you specifically. This is a much smaller problem and, unlike the first, it is largely solvable.

This guide is about the second. It is worth being clear about that, because a great deal of advice conflates them and ends up recommending Tor as though it protected your transaction history, which it does not.

If your concern is the first problem, the honest summary is that on a transparent chain, privacy is a discipline rather than a default, and the section below on what cannot be fixed covers what that means.

What a hosted explorer actually learns

When you load an explorer page, the operator receives the same things any website receives: your IP address, your user agent, the page you requested, a timestamp, and whatever their analytics and advertising scripts collect.

The page you requested is the significant one, because on an explorer the URL contains a blockchain address or a transaction hash. That request is a statement: somebody at this IP address is interested in this address, at this moment.

One such request is nearly meaningless. A pattern of them is not. Repeatedly checking the same address from the same connection is a reasonable basis for concluding that address belongs to you, and no sophisticated analysis is required to reach it.

Whether this matters depends on who the operator is. OKLink is run by an exchange that may separately hold your identity documents. Arkham is an intelligence platform whose product is attributing addresses to entities. Blockchain.com operates a custodial wallet and a KYC exchange alongside its explorer.

We are not alleging that any of them joins these datasets. We are observing that the ingredients exist under one roof, that you cannot verify what happens to them, and that a different choice removes the question entirely.

What actually helps

Use Tor, and prefer an explorer with an onion service. Tor hides your IP from the operator. An onion service means the connection never leaves the Tor network at all, which also removes exit-node exposure. Blockchair, mempool.space, Blockstream.info and xmrchain.net all publish one.

Prefer an explorer that works without JavaScript. A large share of browser fingerprinting is JavaScript-driven, and Tor's strictest security setting disables it entirely. Only a handful of explorers render usable pages in that mode: 3xpl, Blockchair, Blockstream.info and BlockCypher. That this list is so short is a genuine shortcoming of the category.

Avoid logging in. Several explorers offer accounts for watchlists and alerts. A watchlist is a durable, explicit statement of which addresses you care about, attached to an email address. The convenience is real and so is the trade.

Do not use an explorer operated by a party that knows your identity for addresses you control. This is the cheapest improvement available and it costs nothing.

Run your own. This is the complete answer, and the only one that does not require trusting anyone. Otterscan against your own Erigon node for Ethereum; Esplora or mempool.space for Bitcoin. Our self-hosting guide is honest about the cost.

The leak most people never think about

Your wallet queries something to learn your balance, and that something learns everything your wallet asked about.

A light wallet does not run a node. It asks a server — the wallet provider's, an Electrum server, an RPC endpoint — for the state of your addresses. That query contains every address in your wallet, including ones you have never used publicly.

This is a considerably larger disclosure than any explorer lookup, and it happens automatically, every time you open the app, without you doing anything.

Some wallets mitigate it. Bitcoin wallets using client-side block filters download compact summaries and check locally, revealing far less. Wallets that let you point at your own node remove the issue entirely, which is much of the argument for running one.

The reason this belongs in a guide about explorers is proportion. Being careful about explorer lookups while using a light wallet that reports your entire address set to a third party several times a day is straining at a gnat. If lookup privacy matters to you, the wallet is the place to start.

What none of this fixes

Everything above concerns lookup privacy. The chain itself is a different matter and it is worth being blunt about it.

Public blockchains are permanent, complete and open. Every transaction you have ever made is available to anyone, forever, and it will be analysable with better tools in ten years than exist today. The pseudonymity people imagine they have is not a property of the protocol — it is a temporary consequence of nobody having bothered to look.

Once an address is linked to you, the entire history connected to it is linked too, retroactively and permanently. The links come from ordinary places: a withdrawal from an exchange that verified your identity, a donation address posted publicly, a purchase with a delivery attached, reusing an address across contexts.

No explorer choice affects this. Tor does not affect this. The only things that do are behavioural — avoiding address reuse where the chain allows it, being deliberate about what connects to an identified account, understanding that mixing and coinjoin have their own consequences and are not a universal solvent.

And on Monero, the chain simply does not record the data, which is a different approach to the same problem and the reason that chain exists at all.

A proportionate position

Most people do not need to do most of this, and saying so is more useful than a maximalist list nobody follows.

If you are checking a public contract, a protocol treasury or a transaction someone sent you, none of this matters. Use whatever explorer is best for the job and think no further about it.

If you are repeatedly checking addresses that hold meaningful funds of yours, spend five minutes on the cheap improvements: use an explorer with no exchange or analytics business attached, do not create an account, and use Tor if it is convenient.

If your lookups would themselves be revealing — you are a researcher, a journalist, or someone whose interest in an address is itself sensitive — run your own explorer. The cost is real and it is the only option that does not require trusting somebody.

The useful principle is that privacy is a series of proportionate decisions rather than a binary state. Knowing what each choice actually buys you is the point of this guide, and our explorer directory scores every tool on exactly this dimension.