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
Configured Bitcoin Cash networks

Bitcoin Cash (BCH) Block Explorer network directory

Fast Bitcoin Cash (BCH) explorer powered by FloweeBridge and Flowee the Hub Start from the network you need, follow the most common user journeys instantly, and land on a block explorer that feels fast, calm, and trustworthy on first contact.

Start hereOpen default networkAll-network searchRecent activityCompare networksSite statusSite block feedSite transaction feedllms.txtSitemap index
New visitorPick a network, search once, and understand where you are immediately.
Power userJump straight to feeds, mempool, status, or compare views without client-side detours.
Crawler / AIUse sitemap, OpenSearch, RSS, and llms.txt to discover stable canonical routes.
Search default height 946,917Search default best blockSearch default sampled txOpen start hereCompare networksInspect site status
Configured networks2
Reachable now2
Unavailable now0
Default path/mainnet
WOW on first load

Clean hierarchy

The first screen highlights what is live, what to click next, and where every network lives.

Functional depth

Search, blocks, transactions, mempool, stats, status

The explorer covers the workflows different BCH users actually care about without hiding them behind JavaScript widgets.

SEO and archives

Canonical hard links everywhere

Browsers, search engines, archives, and mirrors receive the same crawlable routes and discovery metadata.

AI friendliness

Machine-discoverable paths

llms.txt, OpenSearch, RSS, sitemaps, and stable route patterns make automation easy to aim correctly.

Different kinds of users

What they should instantly feel

Newcomer

I know where to start

The directory names each chain clearly, shows its path segment, and offers obvious first actions.

Payment tracker

I can verify this fast

Search forms and recent activity routes sit above the fold instead of being buried in menus.

Developer

These routes are stable

Canonical URLs, feeds, raw endpoints, and machine-friendly discovery surfaces are easy to copy and automate.

Operator

I can trust what I am seeing

Failover, serving-node details, and status dashboards stay visible instead of hidden in an admin silo.

First-minute launch pad

The best first click depends on your goal

Payment tracker

Find the exact payment trail

Start with a txid or address and let the explorer redirect you to the canonical network detail page.

Search all networks·Recent activity
Chain explorer

See what is moving now

Jump into live blocks and confirmed-transaction samples before drilling into one network.

Recent activity·Compare
Reliability check

Decide whether the backend looks healthy

Inspect site-wide failover visibility before trusting any screenshot, API scrape, or automation run.

Site status·Compare
AI / crawler

Choose the safest machine entry points

Use llms.txt, sitemap, OpenSearch, and feeds so your agent starts from stable canonical routes.

llms.txt·Sitemap
Live proofs

Real first clicks across configured networks

Bitcoin Cash Mainnet

Show me this network right now

Path /mainnet is live, exposes canonical hard links, and gives you immediate block, transaction, and status depth.

Open latest blockOpen sampled tx
Bitcoin Cash Testnet4

Show me this network right now

Path /testnet4 is live, exposes canonical hard links, and gives you immediate block, transaction, and status depth.

Open latest blockOpen sampled tx
Bitcoin Cash Mainnet

Bitcoin Cash Mainnet

Path: mainnet

Primary public BCH network

Height946,917Canonical block link ready
Mempool122 tx51.05664062 KiB
Nodes1Serving mainnet-node-1
Sample txReadyFresh canonical tx link
Address prefixbitcoincash/mainnet
Chain label
main
Availability
Live
Live data available
Best height
946,917
Best block hash
00000000000000000053405ff62188cc851f39ed5a9bb9f5aad8fa4a369cc583
Latest block time
2026-04-15 21:32:40 UTC
Sampled transaction
5a2bd354453afddd933f81ad80a5f0039e55981fae37a31a12252890dace32e9
Serving node
mainnet-node-1
Explorer root
/mainnet
Configured endpoints
  • 127.0.0.1 · hub 1235 · indexer 1234 · mainnet-node-1
Open explorerVerifyLatest blockSampled txStatsStatus
Bitcoin Cash Testnet4

Bitcoin Cash Testnet4

Path: testnet4

Public BCH test network

Height297,505Canonical block link ready
Mempool0 tx0 B
Nodes1Serving testnet4-node-1
Sample txReadyFresh canonical tx link
Address prefixbchtest/testnet4
Chain label
test4
Availability
Live
Live data available
Best height
297,505
Best block hash
000000006cc02048cd08c38f9454c0ab3b0316964f0b6635d3fa0d567e2384f8
Latest block time
2026-04-15 21:52:01 UTC
Sampled transaction
699c9f0c2b82e8253ec73df91f997c5621810073297fa19f338516e95131242f
Serving node
testnet4-node-1
Explorer root
/testnet4
Configured endpoints
  • 127.0.0.1 · hub 21235 · indexer 21234 · testnet4-node-1
Open explorerVerifyLatest blockSampled txStatsStatus
Make the first screen irresistible

Why different users stay instead of bounce

The directory should make each audience feel understood before they know the rest of the information architecture. These walkthroughs turn that goal into explicit route sequences.

Newcomer

I instantly know where to start

Pick the right chain, then follow the shortest path to a meaningful page instead of guessing which menu hides the real explorer.

  1. 1
    Choose a networkUse the labeled chain directory and visible path segments.
  2. 2
    Open the default explorerLand on a network page with live proofs and first-click guidance.
  3. 3
    Search all networksEscalate to cross-network lookup when the chain is not obvious yet.
Payment checker

I can verify this without friction

The site should get a wallet user from uncertainty to a canonical transaction or address route in one move.

  1. 1
    Search all networksResolve a txid, block, or address across every configured network.
  2. 2
    Open a sampled transactionJump straight into a real canonical payment trail.
  3. 3
    Open the site tx feedFinish on a machine-readable surface that mirrors the explorer contract.
Researcher

I can compare before diving deep

A researcher wants orientation first: which chain, how fresh, how busy, and where to go deeper.

  1. 1
    Compare networksScan tip height, cadence, mempool pressure, and halving context side by side.
  2. 2
    Open recent activitySee which configured networks are moving right now.
  3. 3
    Open a network homepageDrop into a chain-specific landing page when one network deserves full attention.
Operator / AI

The route contract is visible

Operational and machine users should see declared discovery surfaces before scraping or trusting anything implicitly.

  1. 1
    Inspect site statusVerify reachability, failover honesty, and serving-node detail across networks.
  2. 2
    Open sitemap indexDiscover stable public entry points without guessing routes.
  3. 3
    Read llms.txtEnd on the plain-text route guide that documents the intended machine workflow.
Discovery surfaces

AI, crawler, and feed entry points

ResourcePathPurpose
Network directory/Canonical site landing page listing every configured BCH network.
All-network search/searchServer-rendered multi-network search helper for fast first use.
Payment-verification guide/verifyCross-network first-minute guide for users who need a trustworthy payment-proof path immediately.
Compare networks/compareSide-by-side chain, mempool, cadence, and health context.
Site status/statusSite-wide Flowee node and failover dashboard.
Site block feed/feed/blocks.xmlRSS feed for bounded recent block updates across networks.
Site transaction feed/feed/transactions.xmlRSS feed for bounded recent confirmed-transaction updates across networks.
OpenSearch description/opensearch.xmlBrowser and tool search integration for the whole deployment.
llms.txt/llms.txtPlain-text guide for LLMs and automation choosing canonical explorer routes.
Landing-page FAQ

Questions the directory now answers up front

Good first impressions reduce second-guessing for users, crawlers, and mirrors.

What is the fastest first click on this site?

Open the default network if you already know the chain you want, or use all-network search when you are starting from a txid, hash, or address and do not yet know which configured BCH network it belongs to.

Why does the directory talk about different user types?

Because wallet users, researchers, operators, and AI agents arrive with different goals. The directory now shows a shortest trustworthy path for each of them instead of forcing everyone through one generic menu.

How does this stay SEO-friendly and AI-friendly at the same time?

The same server-rendered canonical routes are exposed to humans, search engines, archives, and automation. Sitemap, OpenSearch, RSS, and llms.txt are all visible public entry points.

How do I know which network is healthy enough to trust right now?

Use the site status and compare pages. They expose reachability, failover, latency, tip ranges, and health labels across the configured networks.