Public · no login · no API key

The public chain explorer

Everything on this page is read live from CapchaCloud's own public API — the same endpoints anyone can curl. No dashboard, no account, no trust required: the chain tip, the block history, the published signing key, and a one-click way to verify any record are all right here.

Honest scope: this page shows the live public chain state and lets anyone verify a record against the published signing key — the same proof primitives every CapchaCloud certificate relies on. It reads real blocks by height and lists recent history, but it is not a full-text searchable index of every record ever sealed (there is no public search across the underlying private consent/document data — only chain-level metadata is public). Every field below came from a live API response we quoted while building this page, not from assumptions about the shape of the data.

Live chain status

Fetched from GET /api/v1/transparency when this page loaded. Poll it yourself any time — the tip hash must only ever extend, never rewrite.

Couldn't reach CapchaCloud's transparency endpoint just now. This page is a read-only client of that API — it doesn't mean records are lost, just that this browser session can't confirm live status this moment. Try Refresh above.
Loading…

Block explorer

CapchaChain seals batches of sealed records into signed, hash-linked blocks. This lists the most recent blocks from GET /api/v1/chain/blocks and self-checks the whole chain via GET /api/v1/chain/verify.

Couldn't reach the chain endpoints just now — block history is temporarily unavailable in this browser session. Try Refresh above.

Running chain self-check…

HeightBlock hashRecordsProduced at
Loading recent blocks…

Look up a block by height

Every block since height 1 is queryable. Also checks GET /api/v1/chain/anchor?height=N for its Bitcoin/OpenTimestamps anchor status and offers the raw, downloadable .ots proof.

Check a Merkle inclusion proof

Advanced / for developers: given an internal audit-log ID (returned alongside sealed evidence, e.g. in an evidence bundle's chain_inclusion field), GET /api/v1/chain/inclusion returns the exact Merkle path from that record up to a signed block root — independently re-foldable by anyone, offline.

Published signing key

Fetched from GET /api/v1/chain/pubkey. This is the key every CapchaCloud record is signed against — verify any record yourself, offline, against it. Don't take our word that a signature is valid; check it against this key with your own tools.

Couldn't reach the key endpoint just now. Try Refresh above.
Loading…
Algorithm
…
Signer ID
…
Co-signers
…

Public key (base64 SPKI)

…

Verify a record

Paste a CapchaCloud consent-record ID (from a certificate, export, or webhook payload) and check it against POST /api/v1/verify-record. No PII comes back — just whether it exists, whether its stored hash matches what's live right now, and whether the surrounding audit chain is intact. Limited to 30 checks per minute per IP.

How to verify offline yourself

Don't trust this page either — you don't have to. Download an evidence bundle for any sealed record (GET /api/v1/public/evidence-bundle/{id}) and check it with our standalone, dependency-free offline verifier — download verify-evidence-bundle.mjs (Node 18+ built-ins only: node:fs + node:crypto). It makes zero network calls: it recomputes the record's SHA-256 factset hash, checks the Ed25519 envelope signature against the published key above, and — when the record is chain-included — independently re-folds the Merkle path to the signed block root. Every check prints PASS, FAIL, SKIP, or INFO; nothing is silently assumed. Source also lives in the repo at trust-engine/scripts/verify-evidence-bundle.mjs. 

curl -o bundle.json "https://capchacloud.com/api/v1/public/evidence-bundle/<evidence_or_certificate_id>"
curl -O "https://capchacloud.com/verify-evidence-bundle.mjs"
node verify-evidence-bundle.mjs bundle.json --pubkey <the base64 key above>

Prefer to verify the whole append-only chain instead of one record? Same deal, no dependencies: download verify-capchachain.mjs — it walks every block from genesis to the current tip over the public read API, recomputes every block hash, and checks the operator's Ed25519 signature. 

curl -O "https://capchacloud.com/verify-capchachain.mjs"
node verify-capchachain.mjs https://capchacloud.com

Background on what's captured and why it's tamper-evident: Evidence methodology. Live status of the underlying append-only audit chain this explorer reads from: /api/v1/transparency.