StatusConfirmedConfirmed on-chain
Confirmations5,413Based on the current tip
Output total49.99915500 BCHAcross all visible outputs
Outputs55 tokenized outputs
Block301,88600000000e5…0db18c64
Serving nodechipnet-node-1Tip 307,298
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.
52dfd5d7de92dac8ee93d2d10eb6c0c8b4b1beecb70234a9465679c4f18c8171
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 5,413 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
Confirmations5,413
Block301,886
Outputs5
Output total49.99915500 BCH
CashToken outputs5
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.00001000 BCH | d2aba037fd4c83de22cf9eb48863f1efbc2db592e2c754633592ffc24826be4b Custom script | CashTokenNFT |
| 1 | 49.99911500 BCH | 02a75c70c2ce449897fb14bb0157107e3b9afb518578c44b3ae522bed26f005c Custom script | CashTokenNFT |
| 2 | 0.00001000 BCH | 4f091fe3adb0dc9de99d9da51390f9b6f03d6d1cb276abc1efba1611b1f54a83 Custom script | CashTokenNFT |
| 3 | 0.00001000 BCH | 09ea3893bb0800260fa140124f0a97c25281461cc3ad7bcc8710c869408c8a9d Custom script | CashTokenNFT |
| 4 | 0.00001000 BCH | e6deeb8a0df7b5beddd3f9364d1d810747b6a02eb27abea56eb069916d979220 Custom script | CashTokenNFT |
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.