UPTN / block
UPTN block lookup
Look up any UPTN block on Avascan. tx.taxi detects the format, picks the right UPTN explorer, and redirects.
UPTN is an Avalanche L1 subnet routed by tx.taxi through the avalanche-c parent. Because the UPTN L1 is EVM-compatible, addresses use 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 UPTN-related value at tx.taxi/{value} and the router classifies it with the EVM regex layer, probes the avalanche-c parent to confirm, then 302-redirects to the Avascan entry pinned for the UPTN L1. Avascan is the configured explorer for every Avalanche L1 wired into tx.taxi. On this page: UPTN block lookups specifically.
How it works
- Copy your
UPTN block(e.g. a block height or hash). - Paste into the search above or visit
tx.taxi/<your-block>directly. - tx.taxi detects the UPTN format and redirects to Avascan.
Live blocks
1
Frequently asked questions
How is a UPTN address structured?
UPTN runs as an EVM Avalanche L1, so an address is 42 characters: '0x' followed by 40 hex characters. Both the chain and its native gas token use the symbol UPTN, and the same address format applies to wallets and contracts.
Which explorer is configured for UPTN in tx.taxi?
tx.taxi forwards UPTN values to Avascan, the configured Avalanche-L1 explorer for this subnet. The UPTN-specific Avascan path resolves tx hashes, addresses, and block heights via one routing rule.
Is UPTN an EVM Avalanche L1?
Yes. UPTN is registered in tx.taxi as an EVM-compatible Avalanche L1 under the avalanche-c parent, meaning UPTN lookups share Ethereum's hex shapes and pass through the EVM classifier.