First visit confidence
Bitcoin Cash Mainnet is fully server-rendered with hard links, so the first useful click works even when scripts are disabled.
Start hereChain: Bitcoin Cash Mainnet
Bitcoin Cash Mainnet explorer
Primary public BCH network. Built for newcomers, wallet users, researchers, operators, and crawlers who expect hard links, clear routes, and instant confidence without any JavaScript dependency.
Start hereBrowse blocksVerify a paymentRecent transactionsChain statsMempoolStatusRecent block feedTransaction feed
Start with a txPaste a txid or payment address and land on a canonical page immediately.
Need the best first clickUse the chain-specific start-here page when you want the shortest path by goal, not by menu.
Audit a blockOpen the tip, inspect block cadence, and walk backward with crawlable pagination.
Operate safelyCheck live failover state, serving node, feeds, sitemap, and the AI route guide.
Search live height 946,925Search best block hashSearch sampled txOpen start hereInspect live statusRead llms.txt
Try block height 946925, paste a 64-character hash, a wallet-style BCH payment URI, or search for a bitcoincash: address. These chips are live hard links, so the first click already proves the routing model.
Chainmain
Best height946,925
Headers946,925
Indexer tip946,925
Difficulty819,103,041,108.3342
Verification99.99993113%
Mempool txs23
Mempool bytes6.57421875 KiB
See what is happening now
Open the live tip, glance at mempool pressure, and browse the freshest confirmed activity from the canonical landing page.
No hidden client-side dependency
Every page, feed, and discovery route is server-rendered so search engines, mirrors, operators, and low-power devices get the same explorer.
Stable discovery for agents and crawlers
Feeds, sitemaps, OpenSearch, status pages, and llms.txt expose the explorer cleanly to robots, archives, and automation.
Network summary
Latest block spotlight
This network page is canonical for Bitcoin Cash Mainnet and exposes the first decisions most users want to make: verify a payment, inspect the chain tip, check node health, or subscribe to machine-readable updates.
First-minute launch pad
One decisive click for each kind of visitor
Verify a fresh on-chain payment
Jump directly into a freshly sampled confirmed transaction with inputs, outputs, fees, and token details.
Inspect the live tip
Open the newest known block, follow confirmations, and browse backward with hard-link pagination.
Check trust before anything else
See which Flowee node is serving, whether failover is cooling down, and how healthy the backend looks.
Integrate canonical discovery surfaces
Start from stable search, feeds, sitemap, and llms.txt instead of scraping ad-hoc page fragments.
Freshest proof paths
Show me something real immediately
Open a freshly sampled confirmed transaction
This deep link comes from the current bounded block scan and lands on a canonical transaction detail page with fee, inputs, outputs, and token context.
Open the canonical tip route
Use the tip by hash or walk backward with crawlable pagination. Both routes work without JavaScript and stay easy to cite.
Verify the backend before trusting it
Serving-node visibility, failover state, and mempool pressure stay visible so screenshots and automation runs are auditable.
Start from machine-readable discovery
Feeds, sitemap, OpenSearch, and llms.txt are promoted as first-class surfaces instead of hidden implementation details.
Would users love the first minute?
Persona walkthroughs with real hard links
These paths are written from the perspective of different visitors. Each one begins with an obvious link, continues with evidence, and ends with a route that is easy to cite, archive, or automate.
I found the payment immediately
Use one search box, then move from human-readable proof to machine-readable detail without losing the canonical path.
- 1Search a txid or addressResolve directly to the canonical payment page.
- 2Open sampled transactionInspect fees, inputs, outputs, and token context.
- 3Open raw transactionEnd on raw evidence that matches the rendered transaction page.
I can understand the chain fast
The homepage should answer what the tip is, what the cadence feels like, and where deeper analytics live.
- 1Open the current tipStart with the newest canonical block route.
- 2Browse older blocksWalk backward with crawlable pagination instead of infinite scroll.
- 3Open chain statsFinish with cadence, subsidy, and halving context.
I trust what I am seeing
Reliability cues stay visible, so the explorer proves freshness before asking anyone to trust a number on screen.
- 1Inspect statusSee serving-node visibility, reachability, and failover context.
- 2Open mempoolCheck current transaction pressure on the same network.
- 3Open network sitemapConfirm that public discovery routes remain explicit and stable.
The route contract is obvious
Automation should start from declared discovery surfaces rather than guessing routes or scraping random fragments.
- 1Read llms.txtStart from the plain-text route guide.
- 2Open network sitemapDiscover canonical detail pages, feeds, and diagnostics.
- 3Open OpenSearchFinish with a reusable search template for this network.
Recent blocks
| Height | Hash | Time | Difficulty | Confirmations |
|---|---|---|---|---|
| 946925 | 0000000000000000003187bcb6d2c2310f9ca055f7ed20a80b48e737dbdbe0bb | 2026-04-15 23:16:34 UTC | 819,103,041,108.3342 | 1 |
| 946924 | 000000000000000000c57571e2751185b95b512d0ab86d86027fd7593c1c4180 | 2026-04-15 23:01:37 UTC | 817,439,727,351.4182 | 2 |
| 946923 | 00000000000000000031adda9fe186bf849bb1e61a67bc56804268cc4dd5b3dd | 2026-04-15 23:00:02 UTC | 816,485,683,342.0223 | 3 |
| 946922 | 00000000000000000128bf1264c3a4fe46575bc1e38a48818519b3cb6f272a4a | 2026-04-15 22:54:57 UTC | 815,524,633,599.3047 | 4 |
| 946921 | 00000000000000000052489202e57a3ec2ea3402646460605a0d5fa0cc0643a8 | 2026-04-15 22:49:48 UTC | 822,356,195,091.4172 | 5 |
| 946920 | 000000000000000000fb2d97e1841244d70d196b2dd815e49a511662d7c65580 | 2026-04-15 22:05:05 UTC | 820,399,341,078.892 | 6 |
| 946919 | 000000000000000000b2697b6f5cfa9bc295f57a64193954b28555b3f71885b8 | 2026-04-15 22:05:01 UTC | 819,652,768,439.6737 | 7 |
| 946918 | 00000000000000000020a178f758bb047b8c23801bdcf70cf9b5c4467d1b4a52 | 2026-04-15 21:58:47 UTC | 822,835,122,658.1877 | 8 |
Recent confirmed transactions
Crawlable transaction links sampled directly from blocks 946,925 down to 946,925 without any external database.
The current home-page transaction list is a bounded sample. Use the full recent-transactions browse route for the canonical newest-first window.
Crawler and operator entry points
These canonical routes make it easy to discover this network from browsers, crawlers, mirrors, static link collections, and AI agents that prefer explicit route guides.
| Resource | Path | Purpose |
|---|---|---|
| Network homepage | /mainnet | Primary canonical landing page for this configured BCH network. |
| Search helper | /mainnet/search | Hard-link-first search entry point for blocks, transactions, and addresses. |
| Verify guide | /mainnet/verify | Focused first-minute payment-verification route for humans, support desks, and AI agents. |
| Network sitemap | /mainnet/sitemap.xml | Discover recent block pages, bounded transaction pages, feeds, and node diagnostics. |
| OpenSearch description | /mainnet/opensearch.xml | Expose browser search integration for this specific chain label. |
| AI route guide | /llms.txt | Plain-text discovery surface for LLMs, agents, and automation choosing canonical routes. |
| Recent block feed | /mainnet/feed/blocks.xml | Machine-readable recent block updates for polling and feed readers. |
| Recent transaction feed | /mainnet/feed/transactions.xml | Machine-readable recent confirmed-transaction window updates. |
First-minute FAQ
Questions a first-time visitor should not have to ask twice
The landing page should remove uncertainty for humans, search engines, archives, and automation on the very first read.
How do I verify a Bitcoin Cash payment on this explorer?
Use the search box or the sampled transaction link from the homepage. Recognized txids and addresses redirect to canonical detail pages, and raw transaction routes remain one click away for machine verification.
Why is the recent transaction list described as bounded?
This explorer stays honest about what it samples directly from fresh blocks on public Flowee infrastructure. It does not pretend to have infinite history from a hidden external database.
How do I know whether the data is trustworthy right now?
Open the network status page. It exposes serving-node details, failover state, cooldowns, reachability, and indexer lag instead of hiding backend health behind an admin-only screen.
Where should AI agents and crawlers start?
Start from llms.txt, the network sitemap, OpenSearch, and the RSS feeds. Those routes declare the explorer contract more safely than scraping arbitrary rendered fragments.