This page strips block proof down to the shortest trustworthy handoff: canonical route, receipt route, raw block route, timing facts, and the next click for deeper investigation.
0000000007e7df0d541daf9bfa7bf60008caff6fd4ff5fbcdd76d21b53da1812
Use these short statements when another person needs the answer first and the forensic routes second.
On Bitcoin Cash Testnet4, block 192,645 is visible at 2024-03-20 06:55:40 UTC with 120,220 confirmations.
Start with the receipt route, then keep the canonical block page and raw block hex ready only if the reviewer asks for deeper proof.
Use the full block page for transaction context, or network status when freshness and tip movement matter.
Move from this receipt to the full block page when you need the visible transaction table, coinbase note, or page analytics.
Look at status and chain stats before making a freshness-sensitive claim about this block or the current tip.
This receipt shows a small sample only. The full block page keeps the complete visible transaction table and pagination controls.
This route exists to reduce friction when a full block page is more detail than the recipient needs.
Use the receipt page when a person mainly needs the block hash, height, time, confirmation depth, and canonical follow-up routes. Escalate to the full block page for transaction-by-transaction inspection.
It is the human-friendly summary. Machines should still use the raw block route, canonical block page, status page, feeds, sitemap, or llms.txt as appropriate.
Block analytics on the main block page can be intentionally limited to the current transaction page. The receipt repeats that honesty instead of pretending the explorer computed more than it actually did.