Block 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.

000000000000000000c860df3f9307bc93bc952b200ad0996f969751c917c8e7

Full block page Raw block hex Proof text Browse blocks Network status

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.

Receipt meaning

What this block receipt tells you

This receipt shows a block that is already buried under additional chain work, so it is usually the calmest proof route before anyone asks for raw bytes or decoded transactions.

Full block Raw block hex

Height610,240Canonical block shortcut

Confirmations337,553Returned directly with the block

Timestamp2019-11-23 05:44:30 UTCHeader time exposed by Flowee

Transactions9All tx ids currently visible on this block page

ScopeVisible metrics cover the full block.Receipt repeats renderer honesty

Serving nodemainnet-node-1Tip 947,792

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 610,240 is visible at 2019-11-23 05:44:30 UTC with 337,553 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

Canonical block route: /mainnet/block/000000000000000000c860df3f9307bc93bc952b200ad0996f969751c917c8e7
Proof text: /mainnet/block/000000000000000000c860df3f9307bc93bc952b200ad0996f969751c917c8e7/receipt.txt
Binary route: /mainnet/block/000000000000000000c860df3f9307bc93bc952b200ad0996f969751c917c8e7/binary
Height shortcut: /mainnet/block/610240
Previous block: 000000000000000001ab941169fba5574cca68431099e0195628aa5fc9637510
Next block: 0000000000000000014664040a92caef0219491cf9dc61509691822ed4917e2a
Scope note: Visible metrics cover the full block.

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.

Full block·First visible tx

Operator

Check freshness

Look at status and chain stats before making a freshness-sensitive claim about this block or the current tip.

Network status·Chain stats

Visible transactions on this page

Open full block

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.