Find any blockchain transaction in 30 seconds

The 30-second loop

Three steps. The whole flow:

1. Copy the value - a transaction hash, address, block hash, or block height.
2. Paste at tx.taxi/{value} and press enter.
3. Land on the right explorer page, already loaded.

That is the promise. The rest of this guide is how to make it work when the input is ugly, when the chain is unknown, or when the result is not what you expected.

Step 1: Get the value

Wallets, exchanges, and dApps all surface on-chain identifiers in different places. The most common sources:

• Just-broadcast transactions. Right after you sign and submit, your wallet shows a confirmation with a transaction hash. Look for "tx hash", "transaction ID", "txid", "signature", or a "view on explorer" link. Tap or click to expand if the hash is truncated to 0x1234...abcd.
• History tabs. Most wallets have an activity, history, or transactions view. Each entry has a full hash you can copy.
• Exchange withdrawals and deposits. Once a withdrawal is broadcast, the exchange records the on-chain hash. It usually appears under the transaction's detail view in the withdrawal or deposit history.
• Bridges. Cross-chain bridges typically show the source-chain hash and, separately, the destination-chain hash once the relay completes.
• Email receipts and Discord messages. Many tools paste the hash alongside the transaction summary. Grab the full string.

Copy the whole thing. Don't trim, don't paraphrase, don't paste the truncated 0x1234...abcd form - the classifier needs the full hash to match the format.

Step 2: Paste at tx.taxi

Two equivalent entry points:

• Path-style. Open tx.taxi/<value> directly. For example: tx.taxi/0x0000000000000000000000000000000000000000. This produces a 302 redirect to the matching explorer page without any intermediate UI.
• Form-style. Open tx.taxi/ and paste into the input. Press enter. Same routing logic, same destination.

The router runs its classifier the moment it receives the value. Internally that is a stack of prefix checks and regex patterns - 0x plus 40 hex characters means an EVM address, bc1 or 1/3 is Bitcoin, T plus 33 base58 characters is Tron, r plus base58 is XRP, and so on. See the address format by chain cheatsheet for the full pattern list.

For each match, the router looks up the configured primary explorer for that chain - Etherscan for Ethereum, mempool.space for Bitcoin, Solscan for Solana, TRONSCAN for Tron, Tonviewer for TON, and so on - and 302-redirects you to the canonical URL for that object type.

Step 3: You land on the explorer

The redirect drops you on /address/, /tx/, or /block/ on the right explorer. From here, you are looking at the explorer's own UI, with its own tabs, its own search bar, and its own depth of indexing. tx.taxi is done; the explorer takes over.

If the explorer says "transaction not found", three things might have happened:

• Wrong chain guess. The format was ambiguous and the router picked the wrong candidate. Hit back and paste again; tx.taxi can offer the alternates.
• Propagation lag. Brand-new transactions take a few seconds to appear in an explorer's index after they enter the mempool. Wait, refresh.
• Wrong network. A testnet hash will not show up on a mainnet explorer. tx.taxi v1 routes to mainnet by default.

If the address page is blank or shows zero balance, the address is valid but unused on that network. EVM addresses in particular are valid on every EVM chain even when they have no activity on most of them.

When you do not know the chain

The classifier exists exactly for this case. Address and hash formats are designed to be distinct across chain families, so the bytes themselves usually tell you which chain produced them. A few examples:

• A 42-character 0x hex string can only be an EVM-family address. The same key works on every EVM chain, so tx.taxi defaults to a multichain aggregator view rather than committing to one network.
• A base58 string starting with T and 33 more characters is almost certainly a Tron address.
• An 87-88 character mixed-case base58 string with no prefix is overwhelmingly likely to be a Solana transaction signature.
• A bc1 or 1/3 prefix is Bitcoin. ltc1 or LM is Litecoin. D or A is Dogecoin.
• addr1 is Cardano. aleo1 is Aleo. acc:// is Accumulate.

For genuinely ambiguous cases - 64-character hex without a prefix could be Bitcoin or Monero or several other UTXO chains - tx.taxi can present a disambiguation step rather than guess wrong. You pick the chain you meant; the router remembers nothing about the choice.

Speeding up the next lookup

A few habits that turn 30 seconds into 10:

• Bookmark tx.taxi/ as a browser keyword search. Most browsers let you assign a shortcut like tx so that typing tx <value> in the address bar fires off the lookup directly.
• Use the JSON API. The router exposes /api/v1/resolve?q=<value> for the same classification logic, returning JSON. Useful for wallets, bots, and dashboards that want to mirror the routing decision without screen-scraping.
• Combine with multi-chain views. For EVM addresses, the multichain aggregator answer is often the right starting point - you see activity across networks without having to remember which one to check.
• Keep the explorer's URL. Once you are on the explorer, its own URL is now a permanent link. tx.taxi was the on-ramp; the explorer's URL is the bookmark.

What tx.taxi does not do

For clarity:

• tx.taxi does not store balances, transactions, or blocks. It only routes.
• tx.taxi does not sign or broadcast anything. It is read-only by design.
• tx.taxi does not pick "best" explorers in any qualitative sense; it routes to the configured primary explorer per chain, and you are free to point at a different one by going to the chain page directly.

The 30-second loop works because the routing is dumb in the best way. Format in, explorer URL out. Everything else - rendering, indexing, decoding - belongs to the explorer.