Mainnet

Configured chains

Address receipt

Bitcoin Cash Mainnet address bounded proof, condensed for sharing

This page turns the address view into the shortest trustworthy handoff for support, wallet, and compliance conversations: canonical route, receipt route, bounded coverage note, newest observed evidence, and the next click for deeper verification.

bitcoincash:qqu9msmdcs3pgkffumcjxjacmsvmnavencatgvv9u3

One script, two address formats

No visible CashToken history has been observed for this script, so the canonical route stays on the regular address. The token-aware address still resolves here because both formats map to the same locking script. This is a standard pay-to-public-key-hash locking script, so both displayed address formats resolve to the same spendable BCH destination.

Regular addressbitcoincash:qqu9msmdcs3pgkffumcjxjacmsvmnavencatgvv9u3Token-aware addressbitcoincash:zqu9msmdcs3pgkffumcjxjacmsvmnavenc6pmjzrrz
Full address pageProof textVerify this addressRecent transactionsNetwork status
Human-safeShare this route when someone mainly needs a bounded address proof summary instead of the full output table.
Honest scopeThis receipt only summarizes the newest 250 matched outputs currently scanned from live node APIs. It stays explicit about bounded visibility instead of pretending to know infinite history.
Canonical next stepsThe full address page, newest observed transaction, verify guide, and status page stay one click away.
Receipt meaning

What this address receipt tells you

This receipt proves bounded visible activity for this address, not an infinite-history balance. This is a standard pay-to-public-key-hash locking script, so both displayed address formats resolve to the same spendable BCH destination.

Full addressNewest observed tx
CoverageBounded scanThis receipt only summarizes the newest 250 matched outputs currently scanned from live node APIs. It stays explicit about bounded visibility instead of pretending to know infinite history.
Matched outputs250250 scanned right now
Scanned unspent0.00000000 BCH0 visible UTXOs
Script familyP2PKHThis is a standard pay-to-public-key-hash locking script, so both displayed address formats resolve to the same spendable BCH destination.
Tokenized outputs0Alternate token-aware form stays visible
Newest observed block614,594358,669 confirmations
Suggested handoff wording

What to say when you share this address proof

Use these lines to keep address handoff honest about scope, canonical routing, and the two BCH address formats that map to the same script.

For a person

This receipt covers the locking script served here as bitcoincash:qqu9msmdcs3pgkffumcjxjacmsvmnavencatgvv9u3 on Bitcoin Cash Mainnet, with the alternate BCH address format still resolving to the same page.

For a ticket

Coverage is the newest 250 outputs; older history was not included. Cite that limit explicitly when you share this proof.

Best follow-up

Use the newest observed transaction for concrete receive or spend proof, or the full address page for visible output-by-output context.

What this receipt proves

Human-readable bounded-evidence summary

This receipt proves bounded visible activity for this address, not an infinite-history balance.

Coverage honesty

Say what is visible

This receipt only summarizes the newest 250 matched outputs currently scanned from live node APIs. It stays explicit about bounded visibility instead of pretending to know infinite history.

Newest anchor

Start from the freshest observed evidence

Use the newest observed transaction when you need a concrete receive or spend proof.

Human handoff

Share the calm route first

Use the receipt page when someone mainly needs scope, newest observed activity, and canonical follow-up links.

Machine handoff

Escalate carefully

For stronger proof, continue to the canonical address page, newest observed transaction, block route, status page, or verify guide.

Printable checklist

What to include in a support handoff

Address
bitcoincash:qqu9msmdcs3pgkffumcjxjacmsvmnavencatgvv9u3
Regular address
bitcoincash:qqu9msmdcs3pgkffumcjxjacmsvmnavencatgvv9u3
Token-aware address
bitcoincash:zqu9msmdcs3pgkffumcjxjacmsvmnavenc6pmjzrrz
Coverage
Bounded scan
Script family
P2PKH
This is a standard pay-to-public-key-hash locking script, so both displayed address formats resolve to the same spendable BCH destination.
Newest observed confirmations
358,669
Scanned unspent
0.00000000 BCH
Receipt route
/mainnet/address/bitcoincash-qqu9msmdcs3pgkffumcjxjacmsvmnavencatgvv9u3/receipt
Proof text
/mainnet/address/bitcoincash-qqu9msmdcs3pgkffumcjxjacmsvmnavencatgvv9u3/receipt.txt
Verify guide
/mainnet/verify?q=bitcoincash%3Aqqu9msmdcs3pgkffumcjxjacmsvmnavencatgvv9u3

Evidence ladder

Wallet / support

Open newest observed transaction

Move from the bounded address summary into the freshest observed transaction when you need a concrete spend or receive proof.

Newest tx·Verify guide
Researcher

Inspect the full address page

Escalate to the canonical address detail page when you need the visible output rows, spender links, token cells, and pagination controls.

Full address·Recent transactions
Operator

Check freshness

Use status before making freshness-sensitive statements about recently observed address activity.

Network status·Chain stats
Address receipt FAQ

What this compact proof page is for

This route exists for people who need a trustworthy address summary but not the full output table immediately.

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

Use the receipt page when a person mainly needs a bounded summary, newest observed evidence, and canonical next links. Escalate to the full address page for output-by-output inspection and pagination.

Does this receipt claim a full lifetime balance?

No. The receipt repeats the explorer's real coverage. If the address summary is bounded, the receipt says so explicitly instead of inventing an infinite-history balance.

What is the safest citation path after opening this receipt?

For human handoff, cite the receipt and canonical address page together. For concrete payment proof, continue to the newest observed transaction, containing block, raw routes, status page, or verify guide as appropriate.