Space / address
Space address lookup
Look up any Space address on Avascan. tx.taxi detects the format, picks the right Space explorer, and redirects.
Space is an Avalanche L1 subnet routed by tx.taxi through the avalanche-c parent. The Space 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 - identical to anything you would paste against Ethereum. Paste a FUEL-related value at tx.taxi/{value} and the EVM regex classifier picks the object type, the avalanche-c parent prober confirms the route, and tx.taxi 302-redirects to the Avascan entry pinned for the Space L1. Avascan is the configured explorer for every Avalanche L1 wired into tx.taxi. On this page: Space address lookups specifically.
How it works
- Copy your
Space address(e.g. a wallet address). - Paste into the search above or visit
tx.taxi/<your-address>directly. - tx.taxi detects the Space format and redirects to Avascan.
Live addresses
Frequently asked questions
What is the format of a Space address?
Space is an EVM Avalanche L1, so a Space address is 42 characters: '0x' plus 40 hex digits. Native gas on the Space L1 is paid in FUEL, and wallets and contracts share the same address shape.
Which explorer handles Space lookups on tx.taxi?
tx.taxi pins Space (FUEL) inputs to Avascan, the configured Avalanche-ecosystem explorer for this L1. The Space-specific Avascan entry resolves addresses, tx hashes, and block heights from one routing rule.
Is the Space L1 EVM-compatible?
Yes. Space is registered in tx.taxi as an EVM Avalanche L1 under the avalanche-c parent, so FUEL lookups use the same 0x hex formats as Ethereum and run through the standard EVM regex classifier.