What is the fastest way to verify a BCH payment here?

Paste the txid into the network search box. If you only have an address, search that instead and inspect the recent outputs and confirmation depth on the canonical address route.

How do I move from the pretty page to machine-readable evidence?

Use the raw transaction or raw block routes, the recent-transaction feed, the sitemap, or llms.txt. Those routes are stable entry points for scripts and audits.

Why does this guide mention bounded recent transactions?

Because the explorer stays honest about what it can sample directly from recent blocks without an external database. It gives a real current proof path instead of pretending to expose unlimited hidden history.

How do I know whether the answer is fresh enough to cite?

Open the network status page before making freshness-sensitive claims. It exposes serving-node details, failover state, cooldowns, and reachability so you can judge backend health openly.

Verify · Bitcoin Cash Testnet4

Verify a payment

Paste a transaction id, address, payment link, block hash or height: Verify checks whether it exists on Bitcoin Cash Testnet4 and links you to the proof.

Test coins. A match on Bitcoin Cash Testnet4 is not a real BCH payment.

What you will see

FoundIt exists on Bitcoin Cash Testnet4: a confirmed or pending transaction, a block, or a valid address. You get its page plus receipts, raw data and proofs.
Not verifiedIt is not on Bitcoin Cash Testnet4 yet, or the explorer could not check right now. The page says which.
Not recognisedThe value is not a txid, block hash, block height, BCH address or BCH payment link.

Search jumps straight to the matching page. Verify stops to show the answer and the proof links first.

More ways to prove a payment: receipts, raw data, feeds

Three-step proof ladder

Find it. Paste the value above, or use search, to reach the canonical transaction, address or block page.
Share it. Receipt pages are short, print-friendly summaries. Raw hex and merkle proofs let anyone check the same data independently.
Check freshness. Before citing a time-sensitive answer, confirm on the status page that the backend is answering.

Search this network Open latest block Open raw transaction Check node health Open network sitemap llms.txt

Verification FAQ

What is the fastest way to verify a BCH payment here?: Paste the txid into the network search box. If you only have an address, search that instead and inspect the recent outputs and confirmation depth on the canonical address route.
How do I move from the pretty page to machine-readable evidence?: Use the raw transaction or raw block routes, the recent-transaction feed, the sitemap, or llms.txt. Those routes are stable entry points for scripts and audits.
Why does this guide mention bounded recent transactions?: Because the explorer stays honest about what it can sample directly from recent blocks without an external database. It gives a real current proof path instead of pretending to expose unlimited hidden history.
How do I know whether the answer is fresh enough to cite?: Open the network status page before making freshness-sensitive claims. It exposes serving-node details, failover state, cooldowns, and reachability so you can judge backend health openly.