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:qqphhlrg92jp4vxjrufq65h8flfqntm8wy2lrzehph
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.
Use these lines to keep address handoff honest about scope, canonical routing, and the two BCH address formats that map to the same script.
This receipt covers the locking script served here as bitcoincash:qqphhlrg92jp4vxjrufq65h8flfqntm8wy2lrzehph on Bitcoin Cash Mainnet, with the alternate BCH address format still resolving to the same page.
Coverage reflects every matched output currently available for this script, still from live node APIs.
Use the full address page or verify guide next when someone needs deeper context than this bounded summary.
This receipt proves every address match currently available for this address on this network.
This receipt summarizes every matched output currently available for this address, still from live node APIs.
No newest observed transaction is currently exposed.
Use the receipt page when someone mainly needs scope, newest observed activity, and canonical follow-up links.
For stronger proof, continue to the canonical address page, newest observed transaction, block route, status page, or verify guide.
Move from the bounded address summary into the freshest observed transaction when you need a concrete spend or receive proof.
Escalate to the canonical address detail page when you need the visible output rows, spender links, token cells, and pagination controls.
Use status before making freshness-sensitive statements about recently observed address activity.
This route exists for people who need a trustworthy address summary but not the full output table immediately.
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.
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.
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.