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-28T00:20:11.794Z
manifest sha256ab7d437eb9c9f2cf0f793ea844f81bb0e75af7d6c576b5273db00740c9c5fbe2
html sha256cf7a6ca696004825e8f8dcc7ad315ba07bd79e8f15c29a6ca5da3f2865811bcc
proof⛓ timestamped on-chain
txid23762327272ea89387d6109c867e7d6d62ae0d5c0e65aea5bdb1358bafa73d0d
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 968,664 · 6,105 confirmations
SPV proof & how to re-verify it yourself
block height968664
block merkle rootb45a4bcb27d7a97582ab575e5995b89fa8d575cc6c90e57e67279dc17fb774e5
tx index1083
branch (11)d1fe372a84971416aec40f806fcc5800743880527861da9d55d1bc083a86d565 6df279b3cf67862a93be8696cd0191b54044043fc059f55392bab76d85754b51 6d3a7883556e852133e5df9211b5c73be01669241523c0dbfc12392bebe803c5 a1a0d0676e6394566c53a44ef7f0193d66107fa59f5950cc019daf56e0f04c4a 6a34fea5fe22dcee40f9c3c8e91436a980dc60c6b4dd917f8db5c3c4f26e33dc 35cd95d39d5d12bf92a581ea55c379243e1f65a07298280f43478988e94400f7 10d21454cc46e0c61f8aa3b9dcea88dc925661fe18eace475bb662bbf0912d48 dc578f92c2882d15b969133081c92f73dc4717915cf360fa110861b4d2bc057c 2bc26bf41b6a5d451e31d39bab3a1fd1f1ce09c2b3604d099cec33e6d7ee241f 2cd049df5b6edd119a955b422566bd7d41819142c119f16b13f8fcd7461f8a41 a841aa489ab26f450e3ae174046bab92f875054d2689065dede0ac0c5db95ee5

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 968664 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 ab7d437eb9c9f2cf0f793ea844f81bb0e75af7d6c576b5273db00740c9c5fbe2; it binds the URL, capture time, and the HTML hash. The linked transaction's OP_RETURN carries bsv.cx / web1 / ab7d437eb9c9f2cf0f793ea844f81bb0e75af7d6c576b5273db00740c9c5fbe2, 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