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-25T12:20:12.948Z
manifest sha2564eec4aedbd224803fdfffae87c4584f72605ce1f1c34df44fa3c0f5954a94f4f
html sha256f3d8b906622075b5041426f8a82cb97f64b6ef19c018ba3675eb623d2a00c359
proof⛓ timestamped on-chain
txid06b5a76ac1d5ec38b72ceabf409326133c6c4398ac500e2f78e9fd7a781fefab
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 968,312 · 6,457 confirmations
SPV proof & how to re-verify it yourself
block height968312
block merkle root00854b254f5cf64c3b35115d3d05d40cb9bcb187a403f7572573d17426436c1c
tx index430
branch (10)ce27475ecd9e97b3d1ef7f8bb5a3fd3c8c2ad41f1c84fec180c7481b0369712e f94750b4a6bc35271af964a28af9f6cf97faa8b7b7d09abbd7c7a7dca395ca17 f86d7d4bf1cb44aae2a5a884a0cc5448f37e4595d2471f431faf40adb8c1e9a4 6063df98ad2d924a1ed876e783d3dfb3c8d42800694d5462c88fe3a73ed3709e 68e5f19530240ff5a3d5f4bc44cbc4c2f31aff18609e0d7f1bfdd73368eddbdb dc0b9ccef06955b1df27cfb8950df8b2b66d84de29fd5deae8bfe76bb453914f c6c03371251581a66b2cc89e4a675421847cdb43156c84d4c20405ec26b82701 cc5f5f20566eff1b59950519af8ab43de4b58f369b07616329b4d991dca477ec e9a065efa70726bf711e18380fbdac85b0d27891f8621649db4e549382c685a1 622760cb1229d07b1af8d91557de7a04079cdbe3ed372da010a37ca500f20d9a

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