Avalanche C-Chain / transaction
Avalanche C-Chain transaction lookup
Look up any Avalanche C-Chain transaction on Avascan. tx.taxi detects the format, picks the right Avalanche C-Chain explorer, and redirects.
Avalanche's C-Chain is the EVM-compatible contract chain in the wider Avalanche network. It uses standard 0x-prefixed addresses and hashes, while Avalanche's P-Chain and X-Chain use different identifier formats. tx.taxi's configured primary C-Chain explorer is Avascan, which covers C-Chain plus a number of Avalanche subnets. Paste a C-Chain address, transaction hash, block hash, or block number at tx.taxi/{value} and the router classifies the value and 302-redirects to the matching Avascan page. The same JSON pipeline at /api/v1/resolve is available for programmatic use. On this page: Avalanche C-Chain transaction lookups specifically.
How it works
- Copy your
Avalanche C-Chain 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 Avalanche C-Chain format and redirects to Avascan.
Live transactions
Frequently asked questions
What does an Avalanche C-Chain address look like?
The C-Chain uses the EVM address format: '0x' followed by 40 hex characters. Avalanche's P-Chain and X-Chain use different bech32-style formats and are not the same as C-Chain addresses.
Does tx.taxi cover Avalanche subnets?
tx.taxi routes a number of Avalanche subnet chains in its registry, each with its own configured Avascan explorer instance. See /chains for the current list of supported subnets.
Can I look up an Avalanche P-Chain address with tx.taxi?
P-Chain and X-Chain identifiers use a different format than the C-Chain EVM addresses. tx.taxi v1 targets C-Chain by default; other Avalanche chains route via their own explorer entries when present in the registry.