First visit confidence

Bitcoin Cash Testnet4 is fully server-rendered with hard links, so the first useful click works even when scripts are disabled.

Start here

Machine discovery

Feeds, OpenSearch, sitemap, and llms.txt stay visible as canonical entry points for agents and integrations.

Open llms.txt

Operational honesty

Multi-node failover state, cooldowns, and serving-node details are exposed instead of hidden behind an admin-only view.

Inspect status

Crawlability first

Pages, feeds, and discovery routes are designed to be indexable, archivable, and easy to mirror without JavaScript.

Open sitemap
Block receipt

Bitcoin Cash Testnet4 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.

000000000e7de2607a81ba1ed903e67d0e91699ec801c85cecd91c108b018d72

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

Receipt page

Use this page when a person needs one clean screen with block timing, confirmation depth, and canonical routes.

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.

Height214,830Canonical block shortcut
Confirmations84,198Returned directly with the block
Timestamp2024-08-21 09:30:56 UTCHeader time exposed by Flowee
Transactions1All tx ids currently visible on this block page
ScopeVisible metrics cover the full block.Receipt repeats renderer honesty
Serving nodetestnet4-node-1Tip 299,027
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 Testnet4, block 214,830 is visible at 2024-08-21 09:30:56 UTC with 84,198 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
/testnet4/block/000000000e7de2607a81ba1ed903e67d0e91699ec801c85cecd91c108b018d72
Proof text
/testnet4/block/000000000e7de2607a81ba1ed903e67d0e91699ec801c85cecd91c108b018d72/receipt.txt
Binary route
/testnet4/block/000000000e7de2607a81ba1ed903e67d0e91699ec801c85cecd91c108b018d72/binary
Height shortcut
/testnet4/block/214830
Previous block
0000000003126b3bf0e999854d5aa942bb18506097c2ce9a99c85132c0cc157f
Next block
00000000138110080081f067ffe82c545c7f77d343f9c3138c00d9985768615f
Scope note
Visible metrics cover the full block.
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.