VERIFY · LIVE

Verify a leaf

Paste a leaf hash. This returns its inclusion proof against the current head — and the exact steps to check that proof yourself, in any verifier that speaks RFC 6962.

A leaf hash is the 0x… sha256 in any row of the log. This page carries out the same request a machine makes to /api/v1/public/notary?proof=inclusion&hash=….

Included ✓

This leaf is in the log at position 7217 of 10324, and the audit path below proves it against the head root. You do not have to take that on faith — the steps to check it yourself are below.

Kindsettlement/1
Sourceflashynetwork
Sealed (UTC)2026-09-16T10:00:27.221Z
Refhttps://www.flashynetwork.com/explorer/72db387e-d920-4c17-869d-c1b31fa38dc7
Leaf hash0x54b31407d357eead9568e3eebbd3474e4593de65ce748b7f9304dbf522aef105

Four fields of context and a hash — nothing about who or how much. The ref is where a holder re-fetches the full record and re-hashes it to this same leaf; the log never saw those bytes.

The proof

Head size10324
Head root0x69e811d32015b069f62533afbda223d4f27dff3c3af66f89f84f0f4355f6d881
Audit path
  1. L · 0xc353b2a12488e176d11e…
  2. R · 0x16f710b0c66ef6cd3940…
  3. R · 0x5fb6e41e91d605a2eccf…
  4. R · 0x554dd83b3884f80a6879…
  5. L · 0xd7e26476d7460fc4517e…
  6. L · 0xe60c1a2da41903b04017…
  7. R · 0x3471db7c44b5ee6a0b90…
  8. R · 0x94aacf1ee2bc085ff2e6…
  9. R · 0xb39f7e00a679ae025a10…
  10. R · 0x0aaab7fc73c2ea799c14…
  11. L · 0x81ae8cc84a77e2d21be1…
  12. L · 0x101624fd77afe9f802bf…
  13. L · 0xc3418fa1c95d5584fe6f…
  14. R · 0x62808826bd6f88d6011b…

Check it yourself

The proof is RFC 6962 — Certificate Transparency, byte for byte — so any CT verifier in any language checks it without reading our code. Three ways, from least to most independent:

  1. Re-request the machine form and compare: https://flashynetwork.com/api/v1/public/notary?proof=inclusion&hash=0x54b31407d357eead9568e3eebbd3474e4593de65ce748b7f9304dbf522aef105. The root it returns must equal the head root above.
  2. Fetch the whole leaf stream, rebuild the tree, and confirm the root — the head is a number you recompute, never one we ask you to trust.
  3. Keep the head. Later, fetch the new head and a consistency proof between the two; if it passes, the log only grew — nothing was rewritten or removed.

An unsigned head is reproducible, not tamper-evident: recomputing our root checks our arithmetic, not our honesty. Only a cosignature from a party that is not the estate closes that gap, and until one exists the head endpoint says so, with the witness ratio published at zero. See the log for the whole picture.