First visit confidence
Bitcoin Cash Mainnet is fully server-rendered with hard links, so the first useful click works even when scripts are disabled.
Start hereBlock receipt
Bitcoin Cash Mainnet block proof, condensed for sharing
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.
000000000000000000a8d84b9fbb8d42b48f7a53bd8c057ed49004c27f5c6cc9
Human-safeShare this route when someone mainly needs timing, confirmations, and canonical follow-up links.
Machine-safeRaw hex, canonical routes, and status links remain one click away from the same proof surface.
Honest scopeThis receipt summarizes what the explorer can prove directly without inventing hidden history or external-database claims.
Fast block proof
Counterparty
Receipt page
Use this page when a person needs one clean screen with block timing, confirmation depth, and canonical routes.
Height429,763Canonical block shortcut
Confirmations517,467Returned directly with the block
Timestamp2016-09-14 10:54:53 UTCHeader time exposed by Flowee
Transactions1,700All tx ids currently visible on this block page
ScopeVisible metrics cover only the currently rendered transaction page to stay safe on shared public Flowee nodes.Receipt repeats renderer honesty
Serving nodemainnet-node-1Tip 947,229
Suggested handoff wording
What to say when you share this proof
Use these short statements when another person needs the answer first and the forensic routes second.
For a person
On Bitcoin Cash Mainnet, block 429,763 is visible at 2016-09-14 10:54:53 UTC with 517,467 confirmations.
For a ticket
Start with the receipt route, then keep the canonical block page and raw block hex ready only if the reviewer asks for deeper proof.
Best follow-up
Use the full block page for transaction context, or network status when freshness and tip movement matter.
Shareable proof facts
Block receipt facts
When to escalate
Researcher
Inspect transactions
Move from this receipt to the full block page when you need the visible transaction table, coinbase note, or page analytics.
Operator
Check freshness
Look at status and chain stats before making a freshness-sensitive claim about this block or the current tip.
Visible transactions on this page
Open full block- 34080528148aa24b4137902ad5d8206351197177600f72b55a90b97624e9602b
- 12e308b6a5311a587a5e0a56251f32825f706aed0d95f15eb29e9f5639602c04
- b48cc9fcd90e416e65793e7a96874416c9c7a87b0867887e06f8abd629dae1ed
- da36ed93ef75a9790dc81e8ed216b8bd0946956e995d6f640011bb810c06fbcb
This receipt shows a small sample only. The full block page keeps the complete visible transaction table and pagination controls.
Block receipt FAQ
What this compact proof page is for
This route exists to reduce friction when a full block page is more detail than the recipient needs.
When should I share this receipt page instead of the full block page?
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.
Is this receipt page enough for machine verification?
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.
Why does the receipt mention visible-page scope?
Block analytics on the main block page can be intentionally limited to the currently rendered transaction page. The receipt repeats that honesty instead of pretending the explorer computed more than it actually did.