GUNZ / transaction
GUNZ transaction lookup
Look up any GUNZ transaction on Avascan. tx.taxi detects the format, picks the right GUNZ explorer, and redirects.
GUNZ is an Avalanche L1 subnet routed by tx.taxi through the avalanche-c parent pipeline. Because the GUNZ 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 GUN-related value at tx.taxi/{value} and the router classifies the input with its regex layer, probes the configured avalanche-c parent chain to confirm the format, then 302-redirects to the Avascan entry pinned for this specific L1. Avascan is the configured explorer for every Avalanche L1 wired into tx.taxi. On this page: GUNZ transaction lookups specifically.
How it works
- Copy your
GUNZ transaction(e.g. the transaction hash from your wallet). - Paste into the search above or visit
tx.taxi/<your-transaction>directly. - tx.taxi detects the GUNZ format and redirects to Avascan.
Live transactions
Frequently asked questions
What does a GUNZ address look like?
GUNZ runs as an EVM Avalanche L1, so a GUNZ address is the standard 42-character format: '0x' followed by 40 hexadecimal characters. The native gas symbol is GUN, and the same address shape applies to wallets and contracts on the GUNZ L1.
Which explorer does tx.taxi use for GUNZ?
tx.taxi sends GUNZ (GUN) lookups to Avascan - the configured Avalanche-ecosystem explorer for this L1. The Avascan path pinned for GUNZ handles addresses, tx hashes, and block heights from a single routing rule.
Is GUNZ an EVM chain?
Yes. GUNZ is an EVM-compatible Avalanche L1 subnet, classified by tx.taxi under the avalanche-c parent. That means GUN values share the same hex formats as Ethereum, and Avascan renders them with the EVM tx/address/block schema.