EVM · BEAM
Beam block explorer
Look up Beam addresses, transactions, and blocks - routed live to Avascan.
Beam is an Avalanche L1 subnet routed by tx.taxi through the avalanche-c parent. Because the Beam L1 is EVM-compatible, addresses follow the standard 42-character 0x-prefixed hex format and transaction hashes are 0x-prefixed 64-character hex strings - identical in shape to Ethereum values. Paste a BEAM-related value at tx.taxi/{value} and the router classifies it via the EVM regex layer, runs the avalanche-c parent probe to confirm the match, and then 302-redirects to the Avascan entry pinned for the Beam L1. Avascan is the configured explorer for every Avalanche L1 wired into tx.taxi.
Lookup Beam by type
Beam explorers
- Avascan priority 100
Live examples
Try a real Beam lookup. tx.taxi will route it straight to the configured explorer.
1
Frequently asked questions
How are Beam addresses formatted?
Beam runs as an EVM Avalanche L1, so addresses are 42 characters: '0x' followed by 40 hexadecimal characters. Native gas on the Beam L1 is paid in BEAM, and the same address shape is used by wallets and contracts.
What explorer is wired up for Beam in tx.taxi?
tx.taxi routes Beam (BEAM) values to Avascan, the configured Avalanche-ecosystem explorer for this L1. The Beam-specific Avascan path serves tx hashes, addresses, and block heights with one routing rule.
Is Beam an EVM chain?
Yes. Beam is registered in tx.taxi as an EVM-compatible Avalanche L1 under the avalanche-c parent, meaning BEAM lookups share Ethereum's hex shapes and pass through the EVM classifier.