DFK / block
DFK block lookup
Look up any DFK block on Avascan. tx.taxi detects the format, picks the right DFK explorer, and redirects.
DFK is an Avalanche L1 subnet routed by tx.taxi through the avalanche-c parent. Because the DFK 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 anything you would paste against Ethereum. Paste a JEWEL-related value at tx.taxi/{value} and the router classifies it through the EVM regex layer, probes the avalanche-c parent chain for a match, and 302-redirects to the Avascan entry pinned for DFK. Avascan is the configured explorer for every Avalanche L1 wired into tx.taxi. On this page: DFK block lookups specifically.
How it works
- Copy your
DFK block(e.g. a block height or hash). - Paste into the search above or visit
tx.taxi/<your-block>directly. - tx.taxi detects the DFK format and redirects to Avascan.
Live blocks
1
Frequently asked questions
What shape does a DFK address have?
DFK runs as an EVM Avalanche L1, so an address is 42 characters: '0x' followed by 40 hex characters. The native gas symbol on the DFK L1 is JEWEL, and the address shape is identical for wallets and contracts.
Which explorer is configured for DFK on tx.taxi?
tx.taxi pins DFK (JEWEL) lookups to Avascan, the configured Avalanche-ecosystem explorer for this L1. The DFK-specific Avascan entry serves tx hashes, addresses, and block heights from one routing rule.
Does DFK run as an EVM chain?
Yes. DFK is registered in tx.taxi as an EVM-compatible Avalanche L1 under the avalanche-c parent, so JEWEL lookups share Ethereum's hex shape and pass through the same EVM classifier.