Aurora / transaction
Aurora transaction lookup
Look up any Aurora transaction on Aurorascan. tx.taxi detects the format, picks the right Aurora explorer, and redirects.
Aurora is an EVM-compatible chain that runs as a smart contract on the NEAR Protocol, exposing the standard 0x-prefixed address and hash formats to Ethereum tooling. tx.taxi's configured primary Aurora explorer is Aurorascan at explorer.aurora.dev, used for contract verification, transaction receipts, and token transfers. Paste an Aurora address, transaction hash, block hash, or block number at tx.taxi/{value} and the router classifies the format and 302-redirects to the matching /address/, /tx/, or /block/ page. Because Aurora is EVM-compatible, the same identifier string can also be valid on other EVM chains. On this page: Aurora transaction lookups specifically.
How it works
- Copy your
Aurora 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 Aurora format and redirects to Aurorascan.
Live transactions
Frequently asked questions
How is Aurora related to NEAR?
Aurora is an EVM environment that runs as a smart contract on NEAR Protocol. It uses NEAR for consensus and finality while exposing an Ethereum-compatible execution layer to dapps and wallets.
What does an Aurora address look like?
Aurora uses the standard EVM address format: '0x' followed by 40 hex characters. NEAR-native accounts use a different human-readable format (like name.near) and are not the same as Aurora addresses.
Can I bridge between Aurora and NEAR with tx.taxi?
tx.taxi is a lookup router, not a bridge. It will direct you to the Aurora explorer page for any Aurora address or transaction, where bridge activity is visible if the contract interacted with one.