Lamina1 / address
Lamina1 address lookup
Look up any Lamina1 address on Avascan. tx.taxi detects the format, picks the right Lamina1 explorer, and redirects.
Lamina1 is an Avalanche L1 subnet routed by tx.taxi through the avalanche-c parent. The Lamina1 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 in shape to anything you would paste against Ethereum. Paste a Lamina1 value at tx.taxi/{value} and the EVM regex classifier picks an object type, the avalanche-c parent prober confirms the match, and tx.taxi 302-redirects to the Avascan entry pinned for the Lamina1 L1. Avascan is the configured explorer for every Avalanche L1 wired into tx.taxi. On this page: Lamina1 address lookups specifically.
How it works
- Copy your
Lamina1 address(e.g. a wallet address). - Paste into the search above or visit
tx.taxi/<your-address>directly. - tx.taxi detects the Lamina1 format and redirects to Avascan.
Live addresses
Frequently asked questions
What does a Lamina1 address look like?
Lamina1 is an EVM Avalanche L1, so an address is 42 characters: '0x' followed by 40 hex characters. The native gas symbol configured for the Lamina1 L1 in tx.taxi is L1, and wallets and contracts share the same address shape.
Which explorer is wired up for Lamina1 on tx.taxi?
tx.taxi sends Lamina1 (L1) lookups to Avascan, the configured Avalanche-ecosystem explorer for this subnet. The Lamina1-specific Avascan path resolves addresses, tx hashes, and block heights with one routing rule.
Does Lamina1 run as an EVM chain?
Yes. Lamina1 is registered in tx.taxi as an EVM Avalanche L1 under the avalanche-c parent, so Lamina1 lookups use the same 0x hex shapes as Ethereum and pass through the EVM regex classifier.