Multi-chain lookup

What this does, and what it does not

This is a routing tool rather than an explorer. It recognises the shape of what you paste, picks the right public API, and renders the fields most people actually want — balance, status, fee, confirmations. Then it links you to a full explorer for the rest.

It deliberately uses only APIs that need no key, which is why the chain list is what it is. A keyed API would mean running a server and holding a secret, and we wanted this to keep working even if our own back end is not running. Our API comparison sets out which explorers still offer keyless access and why that group is shrinking.

The upstream operators — Blockstream, mempool.space, Blockchair — will see the request, exactly as they would if you visited their sites. We do not add a layer that would learn anything they do not. If that still matters to you, our privacy guide covers the stronger options, and running your own explorer is the only complete one.

What you can paste

A Bitcoin address in any format — legacy, script or bech32 — returns the confirmed balance, anything unconfirmed, and the transaction count. A Dogecoin address returns the equivalent.

A 64-character hash is treated as a Bitcoin transaction and returns status, total output, fee, fee rate and size. If it is confirmed, you get the block.

An Ethereum address or hash beginning 0x is routed to Blockchair's Ethereum index. Addresses return the balance and whether it is a contract; hashes return sender, recipient, value, fee and success.

A plain number is treated as a Bitcoin block height and returns the block. Height zero is the genesis block, which is worth looking at once.

Reading what comes back

Two fields are worth understanding before you draw a conclusion from them, and both are covered properly in our guides.

On Bitcoin and Dogecoin, the total output of a transaction is almost never the amount paid, because a transaction spends whole unspent outputs and returns the remainder to the sender as change. Our guide on reading a Bitcoin transaction works through why.

The fee rate in satoshis per virtual byte, not the total fee, is what determines when a transaction confirms. If something is stuck, that is the number to look at, and our guide on unconfirmed transactions covers what to do about it.

How the routing actually works

There is no chain selector, because asking someone to pick a network before they can look something up assumes they already know which one they are on — and the people who most need an explorer frequently do not. Instead the tool reads the shape of what you pasted.

A string of exactly sixty-four hexadecimal characters is a transaction hash on most chains, so it is routed to Bitcoin first. A string beginning 0x followed by forty hex characters is an Ethereum address; the same prefix with sixty-four is an Ethereum transaction. A string starting bc1, 1 or 3 is a Bitcoin address, and one starting D with the right length is Dogecoin. A plain number is a block height.

These rules overlap in one place worth knowing about. A bare sixty-four-character hash could be a transaction on Bitcoin, Litecoin, Dogecoin or half a dozen other chains — the format is not chain-specific. We try Bitcoin, and if nothing comes back we tell you the lookup failed rather than silently trying seven more networks and reporting whichever answered. Guessing across chains produces confident wrong answers, and a confident wrong answer about money is worse than an honest failure.

If you know the chain, going straight to a full explorer is always faster. Our chain pages list the right one for each network, and our directory ranks all fifty.

Why this only covers some chains

The chain list here is not a judgement about which chains matter. It is a direct consequence of one design decision: this tool uses only APIs that work without a key.

A key is a secret. Putting one in front-end code means putting it in the page source, where anyone can read it and where it will be scraped within days. So a keyed API forces you to run a server that holds the key and proxies every request — and that server then sees every lookup, which is exactly the property we wanted to avoid.

The result is that chains served by keyless APIs work here, and chains that require a key do not. Bitcoin, Ethereum, Litecoin, Dogecoin, Dash, Bitcoin Cash, XRP, Stellar, Cardano, Zcash, Monero and Solana are all covered by Blockstream, Blockchair, mempool.space or the Solana public RPC. Tron, TON, Base, BNB Chain and the rest would need a key.

That group of keyless APIs has shrunk noticeably. Blockscout moved API traffic behind a key on 1 July 2026, and Etherscan has always required one. Our API comparison tracks the current position and is the page we re-check most often, because it goes stale faster than anything else on this site.

When to stop using this and open a real explorer

Almost immediately, for anything beyond confirming that something happened.

If a Bitcoin transaction is unconfirmed and you want to know how long, you need the projected-block view on mempool.space. This tool will tell you the fee rate; it will not tell you what rate is currently clearing, which is the number that actually answers the question.

If you are looking at an Ethereum contract, you need verified source, and that means Etherscan or Blockscout. Reading a balance tells you nothing about what a contract is permitted to do, which is covered in our guide on checking a contract before you sign.

And if your question spans several transactions — how many, over what period, matching what condition — you want Blockchair, which is the only free tool with a genuine query layer rather than a lookup box.

This tool exists for the first thirty seconds of a problem. After that, a specialist is always better, and the result panel links you to one.

What this costs you in privacy

Less than a hosted explorer, and not nothing, and it is worth being precise about the difference rather than claiming more than is true.

We never see your lookup. The request goes from your browser to Blockstream, Blockchair, mempool.space or the Solana RPC directly, and it does not pass through any server we operate. There is no log to hand over, because there is no log.

Those upstream operators do see it, exactly as they would if you had visited their sites. They see your IP address, your browser details and which address or hash you asked about. That is the same disclosure any explorer lookup involves, and it is the reason our guide on what an explorer learns about you exists.

If the lookup is sensitive — if you are repeatedly checking an address that is yours — use Tor, or better, run your own explorer. Blockstream and mempool.space both publish onion services, and both can be self-hosted. That is the only arrangement where nobody learns anything, and our self-hosting guide is honest about what it costs.

What it cannot do, stated plainly

It cannot reverse, cancel or recover anything. No explorer can, and no service that charges a fee to do so can either. A confirmed blockchain transaction is final, and the only parties who can move the funds are whoever holds the keys.

It has no wallet connection and will never ask for a seed phrase, a private key or a view key. There is no function a read-only lookup could offer that would need one. Any page asking for any of those is stealing from you, and our guide on spotting fake explorers covers how convincing they get.

It cannot tell you who owns an address, because the chain does not record identities. Analytics platforms infer ownership from patterns and off-chain information, and that is inference rather than record.