Henesys / transaction
Henesys transaction lookup
Look up any Henesys transaction on Avascan. tx.taxi detects the format, picks the right Henesys explorer, and redirects.
Henesys is an Avalanche L1 subnet routed by tx.taxi through the avalanche-c parent. The Henesys 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 in shape to values you would paste against any other EVM chain. Paste an NXPC-related value at tx.taxi/{value} and the router classifies it via regex, runs the avalanche-c parent probe to confirm a match, then 302-redirects to the Avascan entry pinned for Henesys. Avascan is the configured explorer for every Avalanche L1 wired into tx.taxi. On this page: Henesys transaction lookups specifically.
How it works
- Copy your
Henesys 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 Henesys format and redirects to Avascan.
Live transactions
Frequently asked questions
How is a Henesys address formatted?
Henesys runs as an EVM Avalanche L1, so a Henesys address is 42 characters: '0x' followed by 40 hex digits. The native gas symbol on Henesys is NXPC, and the same address shape covers wallets and contracts on the L1.
Where does tx.taxi send Henesys lookups?
tx.taxi forwards Henesys (NXPC) values to Avascan - the configured Avalanche-ecosystem explorer for this subnet. The Henesys-specific Avascan entry resolves addresses, tx hashes, and block heights from a single routing rule.
Is Henesys an EVM-compatible chain?
Yes. Henesys is classified in tx.taxi as an EVM Avalanche L1 under the avalanche-c parent, which means NXPC values share the same hex shapes as Ethereum and are recognised by the standard EVM regex layer.