StraitsX / transaction
StraitsX transaction lookup
Look up any StraitsX transaction on Avascan. tx.taxi detects the format, picks the right StraitsX explorer, and redirects.
StraitsX is an Avalanche L1 subnet routed by tx.taxi through the avalanche-c parent. Because the StraitsX L1 is EVM-compatible, addresses follow 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 Ethereum or any other EVM chain. Paste a StraitsX value at tx.taxi/{value} and the router classifies it via the EVM regex layer, probes the avalanche-c parent to confirm the route, then 302-redirects to the Avascan entry pinned for the StraitsX L1. Avascan is the configured explorer for every Avalanche L1 wired into tx.taxi. On this page: StraitsX transaction lookups specifically.
How it works
- Copy your
StraitsX 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 StraitsX format and redirects to Avascan.
Live transactions
Frequently asked questions
What format do StraitsX addresses use?
StraitsX is an EVM Avalanche L1, so a StraitsX address is 42 characters: '0x' followed by 40 hex characters. The native symbol configured for the StraitsX L1 in tx.taxi is STX, and the address shape covers wallets and contracts alike.
Which explorer does tx.taxi pick for StraitsX?
tx.taxi routes StraitsX (STX) lookups to Avascan, the configured Avalanche-ecosystem explorer for this L1. The StraitsX-specific Avascan path resolves addresses, tx hashes, and block heights via one routing rule.
Does StraitsX run as an EVM chain?
Yes. StraitsX is registered in tx.taxi as an EVM Avalanche L1 under the avalanche-c parent, which means STX lookups use the same 0x hex formats as Ethereum and resolve through the standard EVM classifier.