RECEIPT EXPLORER
Inspect execution receipts like a transparency log explorer
Search the on-site example catalog, paste arbitrary JSON, or open a receipt from URL parameters. Signature checks use WebCrypto only; optional key discovery fetches published keys only, not your receipt body.
1 Paste receipt · 2 Verify signature · 3 Inspect result
Paste receipt JSON
Edit the canonical JSON below. Aliases such as signature / policy_hash are accepted for offline verify (same canonical bytes as the CLI).
Formatted JSON
-
Recent receipts
Loads from GET /v1/receipts when your log exposes it; otherwise shows catalog preview. Click a row to load that receipt into the viewer.
| Timestamp | Surface | Decision | Receipt id |
|---|
Merkle inclusion proof
Optional key discovery performs a GET of published public keys only. To load from a self-hosted receipt log, use ?receipt_id=... and optional receipt_log=https://host (GET /v1/receipts/:id).
ABOUT RECEIPTS
Offline receipt verification
This page focuses on operational verification workflow. Receipt field semantics and invariants are canonical in /protocol/receipts and /protocol/spec.
Use this explorer to validate receipts locally; use /docs/verification for verification procedure details and /execution-flow for request-to-receipt lifecycle context.
PROOF
Independent decision proof
Cryptographic verification on this page runs only in your browser. Optional key discovery fetches published keys only, not your receipt body. For the full lifecycle from request to receipt, see execution authorization flow; for keys, canonical JSON, and Ed25519 details, see the verification guide.
LEARN MORE
Related protocol documentation
- Protocol specification - system overview and TG-01
- Receipt verification guide - keys, canonical JSON, Ed25519
- Execution authorization flow - request to signed receipt
- Receipt schema - wire fields and semantics
- Protocol playground - generate and tamper in-browser
trigguard verify-receipt- CLI parity- Execution authorization gateway (Gate)