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.

d66273585bd3bfbc5d778b613b2ff2a2cd7f3f6ffd09cdcfa1633e640384eb10

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.
Receipt meaning

What this payment receipt tells you

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.

StatusConfirmedConfirmed on-chain
Confirmations585,971Based on the current tip
Output total19.93190000 BCHAcross all visible outputs
Outputs2No CashToken outputs visible
Block366,5900000000000…3e652bac
Serving nodemainnet-node-1Tip 952,560
Suggested handoff wording

What to say when you share this payment proof

These sentence patterns keep the first explanation calm, bounded, and easy to verify.

For a person

This transaction is confirmed on Bitcoin Cash Mainnet with 585,971 confirmations.

For a ticket

Share the receipt route first, then add the canonical transaction page, raw transaction, or containing block only if the reviewer needs deeper evidence.

Best follow-up

Use the containing block when inclusion depth matters, and raw transaction only when someone needs byte-level verification.

StatusConfirmed
Confirmations585,971
Block366,590
Outputs2
Output total19.93190000 BCH
CashToken outputs0
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 current tables.

Merkle proof

Inclusion path for this tx

Download the merkle proof in hex or binary format.

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, raw transaction hex, and merkle proof.

Printable checklist

What to copy into a ticket, email, or PDF

Transaction id
d66273585bd3bfbc5d778b613b2ff2a2cd7f3f6ffd09cdcfa1633e640384eb10
Status
Confirmed
Confirmations
585,971
Output total
19.93190000 BCH
Receipt route
/mainnet/tx/d66273585bd3bfbc5d778b613b2ff2a2cd7f3f6ffd09cdcfa1633e640384eb10/receipt
Proof text
/mainnet/tx/d66273585bd3bfbc5d778b613b2ff2a2cd7f3f6ffd09cdcfa1633e640384eb10/receipt.txt
Transaction binary
/mainnet/tx/d66273585bd3bfbc5d778b613b2ff2a2cd7f3f6ffd09cdcfa1633e640384eb10/tx.bin
Merkle proof
/mainnet/tx/d66273585bd3bfbc5d778b613b2ff2a2cd7f3f6ffd09cdcfa1633e640384eb10/merkleproof.bin
Merkle proof binary
/mainnet/tx/d66273585bd3bfbc5d778b613b2ff2a2cd7f3f6ffd09cdcfa1633e640384eb10/merkleproof.bin
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.