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