StatusConfirmedConfirmed on-chain
Confirmations1,057Based on the current tip
Output total0.00762576 BCHAcross all visible outputs
Outputs61 tokenized output
Block326,317000000002c…2ae6f97b
Serving nodechipnet-node-1Tip 327,373
Verification receipt
Bitcoin Cash Chipnet 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.
2cb97b1276272b8d11d7bc72f7363a30d815fd3c59575f0afdc45d0a46c1e0fe
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.
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 Chipnet with 1,057 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
Confirmations1,057
Block326,317
Outputs6
Output total0.00762576 BCH
CashToken outputs1
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.
Stable link for people
Share the receipt or canonical transaction route when a human needs the cleanest handoff.
Stable link for machines
Open the raw transaction hex when another system needs to verify bytes rather than current tables.
Inclusion path for this tx
Download the merkle proof in hex or binary format.
Use when confirmation depth matters
The containing block route is one click away for inclusion and confirmation-depth checks.
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
Shareable proof facts
Transaction receipt facts
Visible destination preview
First outputs
| # | Amount | Address or script | Tokens |
|---|---|---|---|
| 0 | 0.00132440 BCH | bchtest:qqw42nlxkde2vmn59yc3zwa9ya2utury7g9a07qldy | — |
| 1 | 0.00001000 BCH | bchtest:zqw42nlxkde2vmn59yc3zwa9ya2utury7gzhuqwejh | CashTokenNFT |
| 2 | 0.00000000 BCH | fa5748678b8804c0c00f23f897f1870d07af4804874c01c200a745a2c54d7603 OP_RETURN | — |
| 3 | 0.00000600 BCH | bchtest:qp8njaa9a3ahg7259s5qajnce526n0rttsy4yfyz4r | — |
| 4 | 0.00565682 BCH | bchtest:qzew3dqcsj0guwe5y3uxf9q2xs5ajgy9lce8xg8xlq | — |
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.