Apertum / address
Apertum address lookup
Look up any Apertum address on Avascan. tx.taxi detects the format, picks the right Apertum explorer, and redirects.
Apertum is an Avalanche L1 subnet routed by tx.taxi through the avalanche-c parent. The Apertum L1 is EVM-compatible, which means addresses use the standard 42-character 0x-prefixed hex format and transaction hashes are 0x-prefixed 64-character hex strings - the same shapes you would paste against Ethereum or any other EVM chain. Paste an APTM-related value at tx.taxi/{value} and the regex classifier identifies it, the avalanche-c parent prober confirms the route, and tx.taxi 302-redirects to the Avascan entry pinned for the Apertum L1. Avascan is the configured explorer for every Avalanche L1 wired into tx.taxi. On this page: Apertum address lookups specifically.
How it works
- Copy your
Apertum address(e.g. a wallet address). - Paste into the search above or visit
tx.taxi/<your-address>directly. - tx.taxi detects the Apertum format and redirects to Avascan.
Live addresses
Frequently asked questions
What does an Apertum address look like?
Apertum is an EVM Avalanche L1, so addresses are 42 characters: '0x' followed by 40 hex digits. Native gas on the Apertum L1 is paid in APTM, and the same address format covers wallets and smart contracts.
Which explorer does tx.taxi route Apertum to?
tx.taxi sends Apertum (APTM) inputs to Avascan, the configured Avalanche-L1 explorer for this subnet. The Apertum-pinned Avascan path covers addresses, tx hashes, and block heights from a single routing rule.
Is Apertum EVM-compatible?
Yes. Apertum is registered in tx.taxi as an EVM Avalanche L1 under the avalanche-c parent, so APTM lookups use the same 0x hex formats as Ethereum and pass through the EVM regex classifier.