Lamina1 Identity / address
Lamina1 Identity address lookup
Look up any Lamina1 Identity address on Avascan. tx.taxi detects the format, picks the right Lamina1 Identity explorer, and redirects.
Lamina1 Identity is an Avalanche L1 subnet routed by tx.taxi through the avalanche-c parent. The Lamina1 Identity 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 an LID-related value at tx.taxi/{value} and the EVM regex classifier identifies it, the avalanche-c parent prober confirms the route, and tx.taxi 302-redirects to the Avascan entry pinned for the Lamina1 Identity L1. Avascan is the configured explorer for every Avalanche L1 wired into tx.taxi. On this page: Lamina1 Identity address lookups specifically.
How it works
- Copy your
Lamina1 Identity address(e.g. a wallet address). - Paste into the search above or visit
tx.taxi/<your-address>directly. - tx.taxi detects the Lamina1 Identity format and redirects to Avascan.
Live addresses
Frequently asked questions
How is a Lamina1 Identity address shaped?
Lamina1 Identity is an EVM Avalanche L1, so an address is 42 characters: '0x' followed by 40 hex digits. The native gas symbol for the Lamina1 Identity L1 is LID, and the same address format covers wallets and contracts.
Where does tx.taxi send Lamina1 Identity lookups?
tx.taxi forwards Lamina1 Identity (LID) values to Avascan, the configured Avalanche-L1 explorer for this subnet. The Lamina1 Identity-specific Avascan path serves tx hashes, addresses, and block heights from one routing rule.
Is Lamina1 Identity EVM-compatible?
Yes. Lamina1 Identity is registered in tx.taxi as an EVM Avalanche L1 under the avalanche-c parent, so LID lookups share Ethereum's hex shapes and pass through the standard EVM regex classifier.