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 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
Verification receipt

Bitcoin Cash Mainnet payment proof, condensed for sharing

This receipt page strips the transaction view down to the shortest trustworthy proof trail: canonical link, receipt link, raw route, status, and containing block context when available.

dfd45fd7ba1ea77551fb070ede17c8cd4a67fdc21b516bc59dbfbaed4de7c944

Human-safeShare this page when someone needs a quick answer without parsing the full transaction tables.
Machine-safeRaw hex, block links, and status links remain one click away from the same canonical route family.
Honest by designPending transactions stay clearly marked as mempool entries instead of being overstated as settled.
StatusConfirmed
Confirmations37
Block946,921
Outputs14
Output total0.18111087 BCH
CashToken outputs13
What this receipt proves

Human-readable evidence summary

This receipt proves the transaction is visible on-chain for this network and links directly to the canonical block, raw hex, and status context needed for stronger verification.

Canonical route

Stable link for people

Share the receipt or canonical transaction route when a human needs the cleanest handoff.

Raw route

Stable link for machines

Open the raw transaction hex when another system needs to verify bytes rather than rendered tables.

Containing block

Use when confirmation depth matters

The containing block route is one click away for inclusion and confirmation-depth checks.

Freshness context

Know what this does not prove

For stronger proof, pair this receipt with the containing block and raw transaction hex.

Shareable proof facts

Receipt facts

Receipt route
/mainnet/tx/dfd45fd7ba1ea77551fb070ede17c8cd4a67fdc21b516bc59dbfbaed4de7c944/receipt
Canonical transaction
/mainnet/tx/dfd45fd7ba1ea77551fb070ede17c8cd4a67fdc21b516bc59dbfbaed4de7c944
Raw proof
/mainnet/tx/dfd45fd7ba1ea77551fb070ede17c8cd4a67fdc21b516bc59dbfbaed4de7c944/raw
Network
Bitcoin Cash Mainnet
Transaction id
dfd45fd7ba1ea77551fb070ede17c8cd4a67fdc21b516bc59dbfbaed4de7c944
Status
Confirmed on-chain
Confirmations
37
Block
946,921 · 00000000000000000052489202e57a3ec2ea3402646460605a0d5fa0cc0643a8
Block time
2026-04-15 22:49:48 UTC
Network status
/mainnet/status
Visible destination preview

First outputs

#AmountAddress or scriptTokens
00.05059164 BCH2e5bfad1ee0bebabbdb5c916a5d2a46a469f9f890ed8626bd5ae2c92dc2fdb09
Custom script
Category: 34e3fe26352632e8b331e679c73721f527afdf975bce4a64fddc25c6c867cd4dAmount: 853,887,854FT: Yes
10.04642187 BCHb8b381dac4056d3e2bbfe47430d8c595c8aa7d95ffe9d6dccb41992c7de74b39
Custom script
Category: 34e3fe26352632e8b331e679c73721f527afdf975bce4a64fddc25c6c867cd4dAmount: 783,510,212FT: Yes
20.02590557 BCH4cac20979564f407db7f232cc1225a6def71695f0cc6a6c2718d286b6107f64e
Custom script
Category: 34e3fe26352632e8b331e679c73721f527afdf975bce4a64fddc25c6c867cd4dAmount: 437,235,197FT: Yes
30.01817147 BCHb60d1bbfab95f69e488a784c138826a133f584dbe0049231f93f7360ee245d9b
Custom script
Category: 34e3fe26352632e8b331e679c73721f527afdf975bce4a64fddc25c6c867cd4dAmount: 306,698,892FT: Yes
40.01106310 BCHb8c575b306ab91487783261eed080c294ce6d61b42cc483b8ab9f35ae339afa7
Custom script
Category: 34e3fe26352632e8b331e679c73721f527afdf975bce4a64fddc25c6c867cd4dAmount: 186,723,488FT: Yes

The full transaction page retains every input, output, prevout note, and raw script detail when deeper analysis is needed.

Receipt FAQ

What this compact proof page is for

This route exists to reduce friction when a full transaction page is more detail than the recipient needs.

When should I share this receipt page instead of the full transaction page?

Use the receipt page when a person mainly needs status, time, block context, and canonical links. Escalate to the full transaction page when they need to inspect inputs, outputs, or token detail.

Is this receipt page enough for machine verification?

It is the human-friendly summary. Machines should still use the raw transaction route, containing block route, status page, sitemap, feeds, or llms.txt as appropriate.

How is confirmation depth shown here?

Confirmed transactions show confirmation count relative to the currently visible best height on this network. Mempool transactions stay clearly marked as pending.