Bitcoin Cash (BCH) Block ExplorerFast Bitcoin Cash (BCH) explorer powered by FloweeBridge and Flowee the Hub

First visit confidence

Bitcoin Cash (BCH) Block Explorer is fully server-rendered with hard links, so the first useful click works even when scripts are disabled.

Start here

Machine discovery

Feeds, OpenSearch, sitemap, and llms.txt stay visible as canonical entry points for agents and integrations.

Open llms.txt

Operational honesty

Multi-node failover state, cooldowns, and serving-node details are exposed instead of hidden behind an admin-only view.

Inspect status

Crawlability first

Pages, feeds, and discovery routes are designed to be indexable, archivable, and easy to mirror without JavaScript.

Open sitemap
Start here

Get from uncertainty to proof in under a minute

This page is the shortest path into the explorer when you are not sure where to begin. It answers what you already have, which configured Bitcoin Cash network to open, and which human-safe or machine-safe route to cite next.

All-network searchVerification guideOpen default networkCompare networksCheck site statusllms.txt
I have a txid or addressStart from all-network search when the right chain is still unclear.
I need trust before detailsOpen site status or compare networks before citing freshness-sensitive facts.
I am an AI agent or crawlerBegin with sitemap, OpenSearch, feeds, and llms.txt instead of scraping guesses.
Search default live heightSearch default best blockSearch sampled txCompare configured networksInspect site status
Configured networks2
Reachable now2
Unknown chain route/search
Human proof guide/verify
Decision board

Choose the route that matches what you already know

Address or BCH URI

Turn it into proof

Wallet users often have an address or payment URI, not a transaction id. The intake pages explain both.

Verify payment·Search all networks
Need the freshest chain view

Compare before drilling down

Researchers and operators often care about which configured network is freshest or busiest before opening a detail page.

Compare networks·Recent activity
Need machine-safe routes

Start from published discovery

Agents, mirrors, and crawlers should begin from public route guides, sitemaps, feeds, and OpenSearch.

llms.txt·Sitemap
Which network should I choose?

Every configured chain exposes an obvious first proof path

Bitcoin Cash Mainnet

bitcoincash

Path /mainnet is live. Use the chain-specific start page when you want the shortest trustworthy path into blocks, payments, receipts, status, and discovery surfaces.

Open start hereSampled tx
Bitcoin Cash Testnet4

bchtest

Path /testnet4 is live. Use the chain-specific start page when you want the shortest trustworthy path into blocks, payments, receipts, status, and discovery surfaces.

Open start hereSampled tx
Persona-first ladders

What each visitor should do first, second, and third

Payment checker

I verify the payment fast

Begin from uncertainty, switch to the right chain, and end on a shareable route instead of a dead-end search state.

  1. 1
    Paste the value onceSearch txids, hashes, BCH addresses, or BCH payment URIs across configured networks.
  2. 2
    Open the proof guideUse the query-aware guide when you need a recommended next click instead of guessing.
  3. 3
    Open the default networkLand on a chain homepage with canonical links, latest proof paths, and status visibility.
Researcher

I orient before drilling down

Start with the deployment shape, then compare freshness and activity, then drop into one chain.

  1. 1
    Read the network directorySee the configured BCH networks and their path segments.
  2. 2
    Compare networksCheck tip height, cadence, mempool, and health side by side.
  3. 3
    Open recent activityMove from deployment overview to current block and transaction movement.
Support / risk

I need the safest citation path

Trust the backend first, then verify the payment, then share the shortest evidence page.

  1. 1
    Inspect site statusCheck reachability, failover honesty, and serving-node visibility across networks.
  2. 2
    Open verification guideResolve the value into the best chain-specific proof path.
  3. 3
    Keep all-network search handyReturn to a broad intake route whenever the chain remains uncertain.
AI agent

The public route contract is explicit

Automation should start from declared discovery and escalate toward canonical detail pages.

  1. 1
    Read llms.txtStart from the plain-text route guide instead of guessing paths.
  2. 2
    Open sitemap indexDiscover canonical site and network surfaces with stable hard links.
  3. 3
    Open OpenSearchReuse the published search template when your agent needs parameterized lookup.
Start-here FAQ

Questions this page should answer immediately

A first-minute page is successful only when it removes hesitation for human visitors and automation alike.

What is the safest first click when I do not know the network?

Use the all-network search route first. It is the shortest intake path for txids, block hashes, BCH addresses, and BCH payment URIs when the correct configured network is still unknown.

What is the best route for a support or merchant handoff?

Use the verification guide to get to a canonical transaction, block, or address page, then share the receipt page or canonical detail page that matches the situation. Status remains available for freshness-sensitive conversations.

How should an AI agent or crawler begin?

Start from llms.txt, the sitemap index, OpenSearch, and the RSS feeds. Those published discovery routes are safer than scraping arbitrary fragments from rendered pages.

Does this page choose the chain for me?

It helps you choose quickly, but it stays explicit about what is known. Compare, status, and all-network search are promoted so the first click remains trustworthy instead of magical.