ADI · ACME
Accumulate (ADI) block explorer
Look up Accumulate (ADI) addresses, transactions, and blocks - routed live to Accumulate Explorer.
Accumulate identifies on-chain entities using URLs rather than opaque hex addresses. An Accumulate Digital Identifier (ADI) looks like acc://example.acme, and sub-accounts use a path-like notation such as acc://example.acme/tokens or acc://example.acme/book. The .acme suffix is the native token namespace for ACME, Accumulate's native token. Transactions are identified by 64-character hex hashes. Paste an acc:// URL or a tx hash at tx.taxi/{value} and the router classifies the format and 302-redirects you to the Accumulate Explorer page. The URL model means the same paste flow works for identities, token accounts, key books, and data accounts.
Lookup Accumulate (ADI) by type
Accumulate (ADI) explorers
- Accumulate Explorer priority 100
Live examples
Try a real Accumulate (ADI) lookup. tx.taxi will route it straight to the configured explorer.
acc://example.acme
acc://example.acme/tokens
Frequently asked questions
What is an ADI on Accumulate?
An ADI (Accumulate Digital Identifier) is a human-readable URL that names an on-chain identity. ADIs can own sub-accounts like token accounts, key books, and data accounts, each addressed as a path under the parent ADI.
Why do Accumulate addresses look like URLs?
Accumulate's design treats on-chain entities as resources addressable by URL, so existing URL tooling and mental models apply. An acc:// URL points to a specific identity, account, or data record on the network.
What is ACME?
ACME is Accumulate's native token. The .acme top-level namespace is reserved for ACME-denominated identities and token accounts, similar in spirit to how .near names work on NEAR.
How are Accumulate transactions identified?
Transactions on Accumulate are identified by 64-character lowercase hex hashes. Paste one at tx.taxi with Accumulate context and the router will land you on the Accumulate Explorer transaction page.