Zeroone / block
Zeroone block lookup
Look up any Zeroone block on Avascan. tx.taxi detects the format, picks the right Zeroone explorer, and redirects.
Zeroone is an Avalanche L1 subnet routed by tx.taxi through the avalanche-c parent. Because the Zeroone L1 is EVM-compatible, addresses use the standard 42-character 0x-prefixed hex format and transaction hashes are 0x-prefixed 64-character hex strings - the same shapes you would paste against Ethereum. Paste a ZERO-related value at tx.taxi/{value} and the EVM regex classifier identifies the object type, the avalanche-c parent prober confirms the chain, and tx.taxi 302-redirects to the Avascan entry pinned for the Zeroone L1. Avascan is the configured explorer for every Avalanche L1 wired into tx.taxi. On this page: Zeroone block lookups specifically.
How it works
- Copy your
Zeroone block(e.g. a block height or hash). - Paste into the search above or visit
tx.taxi/<your-block>directly. - tx.taxi detects the Zeroone format and redirects to Avascan.
Live blocks
1
Frequently asked questions
How is a Zeroone address formatted?
Zeroone is an EVM Avalanche L1, so an address is 42 characters: '0x' followed by 40 hex digits. The native gas symbol on the Zeroone L1 is ZERO, and the same address shape covers wallets and contracts.
Which explorer does tx.taxi route Zeroone to?
tx.taxi pins Zeroone (ZERO) inputs to Avascan, the configured Avalanche-L1 explorer for this subnet. The Zeroone-specific Avascan path serves addresses, tx hashes, and block heights from one routing rule.
Is the Zeroone L1 EVM-compatible?
Yes. Zeroone is registered in tx.taxi as an EVM Avalanche L1 under the avalanche-c parent, which means ZERO lookups share Ethereum's hex shapes and resolve through the standard EVM classifier.