Web-page notarized

A tamper-evident timestamp of a page's content. Pay-per-call — 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-09-30T20:20:12.033Z
manifest sha256d1cfd68ed502b4710c2521b4a2132abb36931ed4599f9d4311d98af2700fbc37
html sha25617bcd38f7dd73dc054b92e824372f51a238fa61a8a77a22f32dff2ea56ba30da
proof⛓ timestamped on-chain
txidfc6bee4017a8ed39a191fe5369042c348860f5b141686a8ccbc4a0e04a1206b8
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 969,072 · 5,697 confirmations
SPV proof & how to re-verify it yourself
block height969072
block merkle root4933e78cb5708be28c0b4e1be73008822ca8b39e844a87a1e83c647857b33aaa
tx index106
branch (9)d7a17b3dcf30909611bb1d8789770f473b34f8a8854049faad0d38e6d1d5e35f 359f035e9719cd27efcc79590a3d4e62dd393a980c1e87a5de5df46edfab2f7c aa0fcdd77b4312c0ba6834aec8ec8e728dfeffaf1b76b5e16be983d7d7f5f419 a2c8fde7a14ecda54479506d9b0a97fd0074d7e65663f93a94a95e5f15f8ec20 72e64301f894c1322ac1febc66781ceaa30d405e51604d937285bb08c8f0392a da4446da01aa6b8dbced4921f77e309abd25159d79610b9cba84fbd69dce8388 a0dc42ae29c7801006b3d01d30da203f703d89a9b99094245bcc6a5f4d12a0e6 8d4d84c5c342f6ff4e2de31a70b9d0403055b2e7bf3c9f90bc9d45367a0da77f 40b3a0e9557b856910c334ee527a771de4435ca33b20bbbb900ba6c5721df767

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 969072 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 d1cfd68ed502b4710c2521b4a2132abb36931ed4599f9d4311d98af2700fbc37; it binds the URL, capture time, and the HTML hash. The linked transaction's OP_RETURN carries bsv.cx / web1 / d1cfd68ed502b4710c2521b4a2132abb36931ed4599f9d4311d98af2700fbc37, and the block's timestamp proves the page looked this way at or before that time.

Other captures of this URL (600)

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