Explorer

The chain explorer

Every public commitment on a2ally, drawn as the chains they form: the Ledger's sealed blocks, and the anchors that independent businesses pin here to prove their own histories. What you are looking at is serialized hashes, counts and signatures — auditable by anyone, meaningful to no one who does not hold the records. The records themselves are never here.

0anchor streams

0events attested by anchors

0anchors pinned

48ledger blocks

129ledger entries

0entries waiting for the next block

Live read model — refreshed from the same public views the API serves. Snapshot: 2026-11-07T01:05:54.706Z · JSON

Latest activity

Anchor streams

Each stream is one owner's hash chain, kept on their own systems and anchored here period by period. An anchor's prev_root must equal the previous anchor's root — break the history and the chain visibly breaks. Streams are numbered, never named: which business a stream belongs to is not published, here or anywhere else on a2ally.

No anchor streams yet.

The Ledger

a2ally's own append-only record, sealed into signed blocks. Each block's prev_hash is the hash of the block before it, so the head block commits to every block before it. Ledger chain: continuous ✓ · the Ledger · verify the whole chain

genesisprev 0000000000000000…0000

→prev = hash

block 34 · 2 entrieshash acf7be36eb472b60…e5b1
root d1e13243f85aa3e2…9197

→prev = hash

block 35 · 1 entryhash 8218997b11538e6c…d485
root 87bb775be8f440b8…c499

→prev = hash

block 36 · 2 entrieshash dc301ccd2bc773dc…42d2
root 62dad6987a7450a6…93ba

→prev = hash

block 37 · 1 entryhash a494994c67d1df4b…e2d4
root 4c043ecb2297b329…6a92

→prev = hash

block 38 · 2 entrieshash c3d096f89400369f…8de9
root 65ffd2947dd191ba…dc18

→prev = hash

block 39 · 1 entryhash 0f5e84630e9a7aa1…7eaf
root 5d157c003fccaa45…5609

→prev = hash

block 40 · 1 entryhash 45f2b1657391f919…4194
root e45b31970ae41763…71de

→prev = hash

block 41 · 2 entrieshash eb5dccf6f00a5a26…44c5
root f86732ec743fafe7…89df

→prev = hash

block 42 · 1 entryhash eb368a4b22bdf9cc…7f6e
root 5ee9adf4bc83aed2…fef4

→prev = hash

block 43 · 2 entrieshash 8e86f0a03a95985c…7945
root 326629e897540782…2b06

→prev = hash

block 44 · 1 entryhash 985eb038f9cb32a9…9e16
root 6bc7a29212214a0c…c79f

→prev = hash

block 45 · 2 entrieshash 46f492861fec9033…69a0
root 79636da797ab08ab…6173

→prev = hash

block 46 · 1 entryhash b9bbca5a5553ab73…8993
root a53b5a59408e1d8a…09f0

→prev = hash

block 47 · 2 entrieshash ed602ab400c4eafa…9c01
root 48fd054ae7e73710…53b6

What you can — and cannot — learn here

Why this exposes nothing: an Anchor client chains its records locally, hashing each record together with a secret per-stream salt (leaf = SHA-256(0x00 ‖ salt ‖ chain hash)). Only the Merkle root of those salted leaves is pinned here. A root is a one-way fingerprint: it cannot be reversed into a record, and even guessing a record exactly does not let anyone check the guess, because the salt is never published — only the owner can reveal a record, with its salt and Merkle proof, and have it verified against the anchored root (POST /v1/anchors/verify-disclosure). The Ledger's private facts are on it the same way, as salted commitments; its public entries are the registrations and listings that are public by design.

What is visible, by design: that a stream exists, how many records it anchored and for what period, when each anchor arrived, and the roots and signatures themselves. Never which business the stream belongs to — streams are numbered, never named. Timing and counts are the price of a public proof — and the whole of it.

Check it yourself: every number on this page is computed from the same read model the API serves at /v1/explore and /v1/ledger; receipts verify against the receipt key published at /v1/anchor-service-info, and the Ledger verifies offline with the CLI.