NEAR · NEAR
NEAR block explorer
Look up NEAR addresses, transactions, and blocks - routed live to PikesPeak.
NEAR has the most human-readable account format in mainstream crypto: addresses are short names like alice.near or root accounts like sub.alice.near, not random hex. Under the hood NEAR also supports 64-character implicit hex accounts for keypair-derived addresses, but the named-account form is what users normally paste. Transaction hashes are base58-encoded strings, distinct from any EVM hex tx hash. Paste a NEAR account, implicit account, or tx hash at tx.taxi/{value} and the router classifies the format and 302-redirects you to the matching page on PikesPeak, NEAR's configured explorer for tx.taxi.
Lookup NEAR by type
NEAR explorers
- PikesPeak priority 100
Live examples
Try a real NEAR lookup. tx.taxi will route it straight to the configured explorer.
Frequently asked questions
What does a NEAR account name look like?
Top-level NEAR accounts end in '.near' on mainnet, like alice.near. Subaccounts are dot-separated, like sub.alice.near. NEAR also supports implicit accounts written as 64 lowercase hex characters with no .near suffix.
Why does NEAR use named accounts?
NEAR's account model lets users register human-readable names that map to keypairs and on-chain state. It is more memorable than a raw hex address and supports nested subaccounts under the same root.
Are NEAR transaction hashes hex?
No. NEAR transaction hashes are base58-encoded strings, which makes them easy to tell apart from EVM hashes. Paste one at tx.taxi and the router will identify it as a NEAR tx and redirect to PikesPeak.
Can I look up NEAR contract calls?
Yes. NEAR smart contracts deploy to ordinary accounts, so the contract account name is what you paste at tx.taxi. PikesPeak shows recent calls, deployed code hash, and on-chain state for the account.