ALEO · ALEO
Aleo block explorer
Look up Aleo addresses, transactions, and blocks - routed live to AleoScan.
Aleo is a zero-knowledge-first L1 where program execution happens off-chain and only succinct proofs are posted on-chain. Aleo addresses are bech32m-encoded strings that always start with the prefix aleo1 and are 63 characters long in total. Transactions and transitions are identified by ids prefixed with at1 and au1 respectively in the canonical encoding. Paste any Aleo value at tx.taxi/{value} and the router classifies the format and 302-redirects to AleoScan. Because Aleo programs can run in private mode, balance and call history for an address are not fully enumerable on-chain in the way they would be on a transparent ledger - the explorer can only show what was made public.
Lookup Aleo by type
Aleo explorers
- AleoScan priority 100
Live examples
Try a real Aleo lookup. tx.taxi will route it straight to the configured explorer.
Frequently asked questions
What does an Aleo address look like?
An Aleo address is a 63-character bech32m-encoded string with the prefix 'aleo1'. The encoding is similar in shape to a Bitcoin bech32 SegWit address but uses Aleo's own human-readable part and longer payload.
Why might Aleo balances not show up on an explorer?
Aleo supports private records that are stored as encrypted commitments rather than plaintext balances. A block explorer can see that records exist and have been spent, but the values and ownership are hidden behind zero-knowledge proofs.
What is the difference between an Aleo transaction and a transition?
A transition is a single proven function call inside an Aleo program. A transaction is a bundle of one or more transitions submitted to the network. AleoScan exposes both views, and tx.taxi will route the matching id format to the correct page.
Is Aleo EVM-compatible?
No. Aleo uses its own zkSNARK-based execution model and the Leo programming language, with a bech32m address format that is unrelated to EVM hex addresses.