Open the live blockchain visualizer to watch Bitcoin and Bitcoin Cash transactions arrive in separate lanes. TX::Watch runs in your browser without an account or a connected wallet. This guide explains how to read the activity you see.
Try a first observation
- Open TX::Watch and check the connection state. An empty lane can mean a quiet feed or an unavailable connection; it does not prove that a network has stopped.
- Watch the BTC and BCH lanes. Each particle is an observed transaction, and its size and color indicate an estimated value band. A block marker is a separate event, not proof that every visible transaction just confirmed.
- Compare the session ledger's counts and fees. These accumulate while the page is open; they are not daily network totals.
- Open the top-transactions tabs to compare fees, estimated value, fee rate, or serialized size. Follow a transaction's explorer link to inspect its inputs, outputs, and confirmation status.
A large particle can include change returning to the sender. A busy lane describes the feed during this session, not the number of people paying or the network's maximum capacity.
An observed session, with its limits
On 12 September 2026, around 20:31 UTC, we read the ledger in a local production build using the live feeds. The session timer showed 4 minutes 16 seconds, and both chains showed Live at capture.
| Displayed measure | BTC | BCH |
|---|---|---|
| Transactions observed | 1,050 | 28 |
| Blocks observed | 0 | 0 |
| Average fee rate, per serialized byte | 0.7 sat/B | 5.3 sat/B |
The BCH protocol panel also identified one CashTokens transaction. These are the recorded screen observations, not a claim about daily traffic or all transactions on either chain. The window includes connection startup, and a live connection at capture does not establish that no events were missed earlier.
Three useful questions follow. First, zero observed blocks in a short sample does not mean either chain stopped producing blocks. Second, a BCH satoshi and a BTC satoshi are fractions of different assets, so their numeric fee rates do not compare dollar costs. Third, a CashTokens marker identifies protocol activity, not a token's legitimacy or value.
To repeat the observation, open a fresh session, record its duration and both connection states, then copy the same three ledger measures. Your counts will differ because the feed is live. Use the ranking tabs and explorer links to investigate individual examples; use Blockspace Lab when you need identical inputs for a controlled comparison.
What the screen shows
BTC and BCH have separate lanes. Each particle represents a transaction observed by the live feed, with size and color cues for value. Block events cross the lane as confirmation markers.
The session ledger accumulates:
- observed transaction count and native value;
- estimated miner fees and a contemporaneous USD conversion;
- transaction shapes such as consolidations and batched payouts;
- high-value transactions;
- CashFusion markers and CashToken activity when the parser can identify them.
These are browser-session totals. Reloading or closing the page starts a new observation window, and activity missed during a disconnection is not reconstructed.
How classification works
The app parses transaction inputs and outputs through a shared analysis pipeline. It can infer shapes from counts and values, identify the canonical CashFusion marker, and decode CashToken prefixes with Libauth.
Those labels are observations, not identities or intent. A many-output transaction may be a batch payment, an exchange withdrawal, or something else. A high USD value may include change. A protocol marker can establish a format without proving who participated.
Data sources and limits
Transaction and block events arrive through the Blockchain.com Socket API. Mempool and fee statistics use Blockchair's stats API. Market prices come from CoinGecko, while CashToken metadata and on-chain context can use Paytaca's BCMR indexer and Chaingraph.
Each source has a different update interval and failure mode. Websocket messages can be missed, API data can be stale, metadata can be absent or conflicting, and USD totals depend on the price available when an event is processed.
TX::Watch is therefore best read as a live sample. Use a full node or established explorer when you need authoritative transaction status, complete history, or consensus validation.
Visualizer, block explorer, or simulator?
| Your question | Where to look |
|---|---|
| What transaction activity is arriving now? | TX::Watch, with its live-session limits |
| Has a specific payment confirmed? | A block explorer or your own node, using the transaction ID |
| Why can a queue keep growing after a traffic spike? | Blockspace Lab, which simulates demand and capacity |
| Which CashTokens appeared in this session? | TokenWatch, which separates protocol activity from token metadata |
TX::Watch reports fee rates per serialized byte (sat/B). Bitcoin wallets commonly quote virtual bytes (sat/vB), so those numbers are not directly interchangeable. The fee-rate explanation walks through the distinction.
Use it as a question generator
The visualizer is most useful when it prompts a better question: Why did the mempool grow? Was that large value mostly change? Did a block clear the fee bands? What distinguishes a token transfer from ordinary BCH?
For controlled experiments with demand and capacity, use Blockspace Lab. For a token-focused view, open TokenWatch.