Web-page notarized

A tamper-evident timestamp of a page's content. Verify any proof — bsv.cx

Rendered page — archived HTML, sandboxed · click to collapse

Html-only render: no scripts or original assets, so it may look unstyled. Not the live page; not endorsed by bsv.cx. ⤢ full screen

off by default; remembered for future views
captured2026-11-07T04:20:08.920Z
manifest sha256785ef9ab162d7e12266e6682eb00fb4da5a354c72a7715af9d2f1ba4d43cd2b1
html sha25664f081065d5abc9780946804344390e91324b0b461e10e8972b8e3fad8672da7
proof⛓ timestamped on-chain
txidc5eeb483ad3c212064da0eafa99656dbbb087a4d331ea7fc165c9540b5806dcb
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 974,424 · 345 confirmations
SPV proof & how to re-verify it yourself
block height974424
block merkle rootd3e5e6134e2e38a5d56b7be1069d3d73be1b3b87889a24f344945d0b86f793ca
tx index397
branch (10)49046bbe569e3539d40e78185f5e0516af68d95bd0462c199b0b9cac0b2cecfe e2d5409b7f0ea4d2c93b41a2b0d8f3910365b580cada02c4b555ab48655afe63 8cb886a3e175cecf991bec3b760b2590a544fc71f0d30ee196d9c13b90626f63 a42a75b3a2fb6dd293d03814bcffd0a8f3b8aa451976d37cd595be20254347fe d09362a9eb9c5aba80e6658d058509e5effa96e4ff3f1d3e61e3dd2fef212c45 a3b3b4b3e5a8ada1765350c081c63ded0f79855a6ab096e93c3b2e3f334b4d6f e6c3898137474948230aaa2445abd1e6e3cc2c979135b833508b553aaef29464 d579ba7d12abcfdb1a410659585ec21c6d6e1432fbd234358db85f4c2d470056 9d05a9826bcacaaee4e99741b0877625c237a3dc69ef1cc8740dd7c0f431602b 3565cdadc2475868749b289d9d09046f4e8e1487e2138bf87717212dda49ffc4

Trust no one: double-SHA256 the txid up this branch — at each level your hash goes left when index is even, right when odd, halving the index each step — to get the block Merkle root, then confirm that root is the header at height 974424 on any block-header source you trust. We verified it against headers we run ourselves; you verify against yours — no explorer, and no bsv.cx, in the trust path.

Prefer to check it against a second independent source? Paste these fields into our public verifier (POST /spv/verify) — it folds the root itself and checks it against headers we sync, so it can only ever make a bad proof fail.

Or take it to your own tools in the ecosystem standard format: BEEF (BRC-62, tx + proof) · BUMP (BRC-74, path only). Any @bsv/sdk client verifies these with no bsv.cx-specific code — Transaction.fromHexBEEF(hex).

keep your copybsv.cx stores this snapshot as a convenience and does not guarantee to host it forever. Download your own copy now — with it you can prove this timestamp yourself, indefinitely, without depending on us.

⬇ page HTML · manifest JSON

Save both. The manifest's SHA-256 is the anchored id, and it binds the HTML hash — so from your saved files you can recompute every hash and match the transaction's OP_RETURN yourself, with no dependence on bsv.cx ever being online.

Verify it yourself: the manifest is the exact JSON whose SHA-256 is 785ef9ab162d7e12266e6682eb00fb4da5a354c72a7715af9d2f1ba4d43cd2b1; it binds the URL, capture time, and the HTML hash. The linked transaction's OP_RETURN carries bsv.cx / web1 / 785ef9ab162d7e12266e6682eb00fb4da5a354c72a7715af9d2f1ba4d43cd2b1, and the block's timestamp proves the page looked this way at or before that time.

Other captures of this URL (179)

← back to bsv.cx · JSON · saved HTML · ⚠ Report