Operations · Bitcoin Cash Mainnet
Status
Is the explorer's backend answering on Bitcoin Cash Mainnet? The summary uses the same reachability rule as /healthz. Call details and node diagnostics follow, collapsed.
Is the stack OK?
Summary
- Bitcoin Cash MainnetReachable
- Tip
- 972,864
- Lag
- One node reporting
- Errors
- 54.1%5,320 / 9,840
/healthz answers ok: 1 of 1 probed node answering.
- mainnet-node-1Preferred127.0.0.1:1235Reachable
- Tip
- 972,864
- Lag
- At tip
- Errors
- 54.1%5,320 / 9,840
OK · unified API reachable; index readiness not probed
Tip agreement, this probe
One node reporting: lag is not measured against another node.
A node is reachable when it answered the status probe. A chain is reachable when at least one probed node is, which is exactly when its /healthz answers ok; otherwise it is degraded and /healthz answers 503. Lag is how far a node's tip is behind the highest tip in the same probe. Error rates count every backend call to the node since the explorer process started; there is no rolling window.
Backend requests
Call timing metrics
Every backend call family the explorer has issued on Bitcoin Cash Mainnet, worst first: highest failure rate, then slowest average. The failure bar is since process start; Last 15 min sits beside it. Open a row for volume, outcome, timing, payload and active-wait detail.
- Call families
- 16
- Completed
- 70,306
- Failed
- 52,077 (74.1%)
- Active now
- 0
- Slowest call
- 12 s
IndexerServiceFindTransactionIdleFailures100.0%Last 15 min100.0%Average11 s
Volume
Outcome
Timing
Payload
Active wait
LiveTransactionServiceGetAddressStatsIdleFailures100.0%Last 15 min100.0%Average111 ms
Volume
Outcome
Timing
Payload
Active wait
LiveTransactionServiceGetAddressHistoryIdleFailures97.0%Last 15 min22.4%Average24 ms
Volume
Outcome
Timing
Payload
Active wait
IndexerServiceGetAvailableIndexersIdleFailures93.5%Last 15 min100.0%Average1 s
Volume
Outcome
Timing
Payload
Active wait
BlockChainServiceGetBlockHeaderIdleFailures26.6%Last 15 min65.1%Average956 ms
Volume
Outcome
Timing
Payload
Active wait
Show the other 11 call families
LiveTransactionServiceGetTransactionsIdleFailures17.7%Last 15 min39.4%Average1 s
Volume
Outcome
Timing
Payload
Active wait
LiveTransactionServiceGetMempoolTxIdsIdleFailures16.5%Last 15 min46.2%Average336 ms
Volume
Outcome
Timing
Payload
Active wait
LiveTransactionServiceGetMempoolInfoIdleFailures14.7%Last 15 min33.3%Average145 ms
Volume
Outcome
Timing
Payload
Active wait
BlockChainServiceGetBlockChainInfoIdleFailures14.6%Last 15 min8.4%Average210 ms
Volume
Outcome
Timing
Payload
Active wait
IndexerServiceGetIndexerLastBlockIdleFailures8.9%Last 15 min59.3%Average693 ms
Volume
Outcome
Timing
Payload
Active wait
BlockChainServiceGetBlockVerboseCompatIdleFailures4.8%Last 15 min15.2%Average401 ms
Volume
Outcome
Timing
Payload
Active wait
BlockChainServiceGetBlockTransactionsIdleFailures0.7%Last 15 min0.0%Average31 ms
Volume
Outcome
Timing
Payload
Active wait
LiveTransactionServiceSearchCashTokenCommitmentIdleFailures0.0%Last 15 min0.0%Average236 ms
Volume
Outcome
Timing
Payload
Active wait
LiveTransactionServiceFindSpentOutputsIdleFailures0.0%Last 15 min—Average10 ms
Volume
Outcome
Timing
Payload
Active wait
BlockChainServiceGetBlockSummariesIdleFailuresNo completed callsLast 15 min—AverageUnavailable
Volume
Outcome
Timing
Payload
Active wait
LiveTransactionServiceSearchMempoolIdleFailuresNo completed callsLast 15 min—AverageUnavailable
Volume
Outcome
Timing
Payload
Active wait
Counts since process start stay, and reset when the BlockExplorer process restarts. The 15-minute rate is what moves when a fix lands. Failure bars run from 0 to 100%. Last 15 min is an em dash when that window has no completed calls, not 0%. Latency bars are relative to the slowest average (11 s). Payload shows observed response data where available.
Node diagnostics: pool, cooldown, last success and failure
Connection pooling keeps backend requests available during busy periods. Slow routes avoid the reserved fast lane whenever more than one session is active.
| Rank | Node | Endpoint | Reachable | Cooldown | Chain | Best height | Indexed tip | Latency | Successes | Failures | Last success | Last failure | Message |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | mainnet-node-1 | 127.0.0.1:1235 Pool 8/8 active Open sessions 8 to backend Busy 1 · Reserved fast 1 | Up | Ready | main | 972,864 | — | 10 ms | 4,520 | 5,320 | 2026-10-14 20:12:29 UTC | 2026-10-14 20:09:23 UTC | OK · unified API reachable; index readiness not probed |
