Alternatives
Blockscan alternatives - other multi-chain address lookups
Looking for Blockscan alternatives? tx.taxi routes any chain lookup, EVM or non-EVM, to the right native explorer without a chain picker.
What you're looking for
People search "Blockscan alternative" for a few reasons. Some want a multi-chain address lookup that includes non-EVM chains - Bitcoin, Solana, Tron, TON, XRP, Sui, Cardano, and others - which an EVM-only aggregator does not cover. Some want a tool that goes directly to the right explorer rather than a search results page. Some just want a cleaner URL pattern, like pasting a value at one base URL instead of filling out a search form.
The category itself is small. Most "block explorer aggregators" are really cross-EVM aggregators that work because every EVM chain uses the same 0x-prefixed address shape. Once you cross into UTXO chains, Solana base58 accounts, Tron base58 addresses, TON workchain addresses, Sui object IDs, or Stellar Stellar addresses, an EVM-only aggregator stops being useful. That gap is where tx.taxi sits.
How tx.taxi fits
tx.taxi is a universal block-explorer router. Paste any chain value at tx.taxi/{value} and the resolver classifies the input by format (regex first, then optional live RPC probing), picks the configured primary explorer for the matched chain, and 302-redirects you straight to the right page. tx.taxi does not maintain its own index, does not host transaction data, and does not duplicate what native explorers already do. It just gets you there faster across many chains than picking a chain by hand.
The positioning relative to Blockscan is straightforward: Blockscan answers "which EVM chains has this 0x address touched". tx.taxi answers "given any chain value, which explorer should I open and where". Those are complementary questions, and tx.taxi actually delegates the first one to Blockscan when the input is an EVM address with no strong single-chain signal. For non-EVM lookups - a Bitcoin address, a Solana signature, a Tron base58 address, a TON workchain address, a Sui object - Blockscan does not apply, and tx.taxi sends you directly to mempool.space, Solscan, TRONSCAN, Tonviewer, SuiVision, or whichever explorer is configured for that chain.
Other multi-chain lookup tools worth knowing
- Blockchair - long-running multi-chain explorer that hosts its own indexes for several chains, EVM and non-EVM.
- OKLink - multi-chain explorer suite that covers many EVM and non-EVM networks under one brand.
- Etherscan family explorers (BscScan, PolygonScan, etc.) - same UX across many EVM chains, useful if you already know which chain you want.
- Blockscout-family explorers - open-source explorer used across many EVM networks, run by chain teams and community operators.
- tx.taxi - the project this site documents: a thin router that classifies a value and redirects to whichever native explorer is configured per chain.
These descriptions are intentionally short. Coverage and supported chains change. Read each project's site before relying on it for a production workflow.
When to use what
If you have an EVM address and you want to see which EVM chains it has activity on, the Blockscan multi-chain aggregator is built for exactly that, and tx.taxi will forward you there when the EVM address could belong to several chains. If you have a non-EVM value - a Bitcoin txid, a Solana signature, a Tron address, a TON workchain address - Blockscan does not apply and tx.taxi routes you directly to the native explorer for the detected chain.
If you want the broadest single-paste experience across both EVM and non-EVM chains, that is the gap tx.taxi is built to fill. Same URL pattern, same routing logic, regardless of which chain your value belongs to.
See also: /chains for the full configured chain list and /api for the JSON resolver that exposes the same routing brain as the redirect.
Frequently asked questions
What is Blockscan used for?
Blockscan is a multi-chain aggregator from the Etherscan family that lets you search a single EVM address across many Etherscan-family explorers and see which chains it has activity on.
Does tx.taxi replace Blockscan?
tx.taxi covers an overlapping but broader use case. Blockscan focuses on EVM chains within the Etherscan family. tx.taxi routes EVM and non-EVM lookups - Bitcoin, Solana, Tron, TON, Sui, Cardano, and more - to the configured primary explorer for each chain.
Why does tx.taxi sometimes redirect EVM addresses to Blockscan?
When an EVM address could exist on multiple chains and there is no strong signal for one chain over another, tx.taxi forwards to the Blockscan multi-chain aggregator so you can pick the chain you actually meant.
Does tx.taxi support non-EVM chains?
Yes. tx.taxi routes addresses, transaction hashes, and block identifiers across Bitcoin, Solana, Tron, TON, XRP, Sui, Cardano, Stellar, Starknet, and several others - not just EVM chains. Blockscan is EVM-only, which is the main gap tx.taxi fills.