APTOS · APT
Aptos block explorer
Look up Aptos addresses, transactions, and blocks - routed live to Aptos Explorer.
Aptos uses a 32-byte account address format written as a 0x prefix followed by up to 64 hex characters. Leading zeros are often omitted, so the same account can appear as 0x1 or as the fully-padded 64-character form. Transactions can be looked up by either their hash or their sequence-bound version number. Paste any Aptos value at tx.taxi/{value} and the router classifies the format and 302-redirects you to the right Aptos Explorer page. The Move-language object model means modules, resources, and accounts all live under the same address namespace, so the same paste flow covers all three.
Lookup Aptos by type
Aptos explorers
- Aptos Explorer priority 100
Live examples
Try a real Aptos lookup. tx.taxi will route it straight to the configured explorer.
Frequently asked questions
How long is an Aptos address?
An Aptos address is 32 bytes, the same size as a Sui address. It is written as '0x' followed by up to 64 hex characters, and leading zeros are commonly omitted when displaying well-known accounts like 0x1.
Why does Aptos use the framework address 0x1?
0x1 is a reserved account that hosts core Move modules of the Aptos framework, including standard libraries for coins, accounts, and on-chain governance. It is the same value as a fully-padded 64-zero address with a single 1 at the end.
How do I look up an Aptos transaction?
Aptos transactions can be referenced by hash (0x-prefixed 64 hex chars) or by their sequential version number. Paste either at tx.taxi and the router will land you on the matching Aptos Explorer tx page.
Is Aptos EVM-compatible?
No. Aptos uses the Move language and a 32-byte address space, which is different from the EVM's 20-byte address space. That is the main reason tx.taxi treats it as a distinct chain rather than routing it through an EVM aggregator.