Chain start here

Bitcoin Cash Chipnet in the first minute

This page is the shortest orientation route for Bitcoin Cash Chipnet . It tells a wallet user what to click first, a researcher where live history begins, an operator how to establish trust, and an Data user which machine-safe surfaces to prefer.

Verify a payment Search this network Network homepage Latest block Sampled tx Status

Need a quick answerUse verify or the receipt routes when someone only needs the shortest trustworthy proof path.

Need detailOpen the canonical block or transaction page for decoded tables, analytics, and raw routes.

Need machine safetyFeeds, sitemap, OpenSearch, raw routes, and llms.txt remain declared public surfaces.

Search live height 311,900 Search best block hash Search sampled tx Stay on start here Read llms.txt

Best height311,900

Recent tx sampleReady

Bounded tx window311,900 → 311,895

Route guide/llms.txt

What do you have in hand?

Choose the task, not the menu

Txid

Prove one payment

Paste the txid when you need the shortest route to confirmations, outputs, fees, receipts, and raw evidence.

Verify·Sampled tx

Address or BCH URI

Show receipt or activity

Search or verify the address to inspect bounded history, unspent outputs, locking script evidence, and the address receipt page.

Search·Verify

Block reference

Prove inclusion

Use the block route when someone shared a height or block hash instead of a txid.

Latest block·Latest blocks

Need backend trust

Establish freshness first

Operators and support teams often need failover and serving-node visibility before citing anything else.

Status·Mempool

Proof ladder

Move from human-readable confirmation to machine-readable evidence

Human proof

Start from a live payment receipt

The receipt page is the shortest support-safe summary, while the canonical tx page keeps full decoded detail one click away.

Open tx receipt Open full tx

History proof

Open the latest block receipt

The block receipt is the shortest proof of chain history, and the full block page keeps decoded transaction context nearby.

Open block receipt Open full block

Operational proof

Check status before freshness-sensitive claims

Status exposes reachability, cooldowns, and serving-node context, while stats explain cadence and subsidy context for the same chain.

Network status Chain stats

Data routes

Open public discovery

Sitemap, feeds, OpenSearch, raw routes, and llms.txt list the public endpoints for this chain.

Network sitemap Transaction feed

Persona walkthroughs

The first three clicks should feel obvious

Wallet user

I answered did this payment happen?

The route should move from uncertainty to a shareable proof without forcing the user to learn the whole explorer first.

1
Paste the txid, address, or BCH URIUse the network verification guide when you already know the chain.
2
Open the transaction receiptShare the condensed proof page when someone mainly needs status, time, and canonical links.
3
Open raw txFinish on raw transaction data for the same transaction.

Researcher

I can understand recent chain history

The chain-specific start page should answer what is happening now, then show where the deeper history routes begin.

1
Open the latest blockStart from the canonical tip route for the current chain.
2
Open older blocksWalk backward with crawlable pagination instead of infinite scroll.
3
Open chain statsContinue to cadence, subsidy, halving, and other chain-level context.

Support / operations

I can hand off proof safely

When another team or counterparty is involved, the shortest calm route is usually better than the densest one.

1
Check status firstVerify backend trust and serving-node context before making freshness-sensitive statements.
2
Share the receipt pageSend a concise proof page before escalating to the full transaction tables.
3
Keep the block receipt handyKeep the block proof path ready in case someone questions confirmation depth or inclusion.

Data access

Public routes are easy to find

Start from published discovery routes, then continue to canonical detail paths.

1
Read llms.txtOpen the plain-text route map.
2
Open the network sitemapFind detail, feed, and status routes.
3
Open OpenSearchUse the published search template for this chain.

Start-here FAQ

Questions this chain-specific page should settle fast

A great first-minute page should remove both confusion and overconfidence.

What is the best first route when I already know the network?

Use the chain-specific verify or search route first. They keep you on the correct network while still guiding you toward the canonical detail or receipt page you actually need.

Why are receipt pages promoted so heavily here?

Because many real-world conversations do not need the full transaction or block tables immediately. Receipt pages give a calmer proof handoff while keeping raw and full-detail routes one click away.

Can this page prove full address history or an infinite balance?

No. The explorer stays honest about bounded windows and bounded explorer coverage. When something is partial, the page should say so explicitly instead of pretending otherwise.

Where are the public data routes?

Start from the network sitemap, feeds, OpenSearch, llms.txt, and status page.