Dexalot / block
Dexalot block lookup
Look up any Dexalot block on Avascan. tx.taxi detects the format, picks the right Dexalot explorer, and redirects.
Dexalot is an Avalanche L1 subnet routed by tx.taxi through the avalanche-c parent. Because the Dexalot L1 is EVM-compatible, addresses follow the standard 0x-prefixed 42-character hex format, and transaction hashes are 0x-prefixed 64-character hex strings - the same shapes you would already paste against Ethereum or Avalanche C-Chain. Paste an ALOT-related value at tx.taxi/{value} and the regex classifier picks an object type, the avalanche-c parent prober confirms it, and tx.taxi 302-redirects to the Avascan entry pinned for the Dexalot L1. Avascan is the configured explorer for every Avalanche L1 wired into tx.taxi. On this page: Dexalot block lookups specifically.
How it works
- Copy your
Dexalot block(e.g. a block height or hash). - Paste into the search above or visit
tx.taxi/<your-block>directly. - tx.taxi detects the Dexalot format and redirects to Avascan.
Live blocks
1
Frequently asked questions
What format does a Dexalot address use?
Dexalot is an EVM Avalanche L1, so addresses are 42 characters long: '0x' plus 40 hex characters. Native fees on the Dexalot L1 are paid in ALOT, and the same address format applies to wallets, validators, and smart contracts.
Which block explorer does tx.taxi pick for Dexalot?
tx.taxi routes Dexalot (ALOT) inputs to Avascan, which is the configured Avalanche-L1 explorer for this subnet. The Dexalot-specific Avascan path handles tx hashes, addresses, and block heights from one routing rule.
Is the Dexalot L1 EVM-compatible?
Yes. Dexalot is registered in tx.taxi as an EVM Avalanche L1 under the avalanche-c parent, so ALOT lookups use the same 0x hex formats as Ethereum and resolve through the standard EVM classifier.