EVM · TIN
Titan block explorer
Look up Titan addresses, transactions, and blocks - routed live to Avascan.
Titan is an Avalanche L1 subnet routed by tx.taxi through the avalanche-c parent. The Titan L1 is EVM-compatible, so addresses follow 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 TIN-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 Titan L1. Avascan is the configured explorer for every Avalanche L1 wired into tx.taxi.
Lookup Titan by type
Titan explorers
- Avascan priority 100
Live examples
Try a real Titan lookup. tx.taxi will route it straight to the configured explorer.
1
Frequently asked questions
How is a Titan address formatted?
Titan is an EVM Avalanche L1, so an address is 42 characters: '0x' followed by 40 hex characters. The native gas symbol on the Titan L1 is TIN, and the same address shape applies to wallets and contracts.
Which explorer does tx.taxi pin Titan to?
tx.taxi routes Titan (TIN) lookups to Avascan, the configured Avalanche-L1 explorer for this subnet. The Titan-specific Avascan path resolves addresses, tx hashes, and block heights from a single routing rule.
Is Titan an EVM Avalanche L1?
Yes. Titan is registered in tx.taxi as an EVM Avalanche L1 under the avalanche-c parent, which means TIN lookups share Ethereum's hex shapes and resolve through the standard EVM regex classifier.