EVM · NUM
Numbers block explorer
Look up Numbers addresses, transactions, and blocks - routed live to Avascan.
Numbers is an Avalanche L1 subnet routed by tx.taxi through the avalanche-c parent. The Numbers L1 is EVM-compatible, so addresses use the standard 42-character 0x-prefixed hex format and transaction hashes are 0x-prefixed 64-character hex strings - the same shapes used by Ethereum and other EVM chains. Paste a NUM-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 Numbers L1. Avascan is the configured explorer for every Avalanche L1 wired into tx.taxi.
Lookup Numbers by type
Numbers explorers
- Avascan priority 100
Live examples
Try a real Numbers lookup. tx.taxi will route it straight to the configured explorer.
1
Frequently asked questions
How is a Numbers address formatted?
Numbers is an EVM Avalanche L1, so a Numbers address is 42 characters: '0x' followed by 40 hex characters. Native gas on the Numbers L1 is paid in NUM, and wallets and contracts use the same address shape.
Which explorer does tx.taxi route Numbers to?
tx.taxi sends Numbers (NUM) lookups to Avascan, the configured Avalanche-L1 explorer for this subnet. The Numbers-pinned Avascan path serves addresses, tx hashes, and block heights from a single routing rule.
Is Numbers an EVM Avalanche L1?
Yes. Numbers is registered in tx.taxi as an EVM Avalanche L1 under the avalanche-c parent, so NUM lookups share Ethereum's hex shapes and pass through the EVM regex classifier.