Operations · Bitcoin Cash Chipnet
Status
Is the explorer's backend answering on Bitcoin Cash Chipnet? The summary uses the same reachability rule as /healthz. Call details and node diagnostics follow, collapsed.
Is the stack OK?
Summary
- Bitcoin Cash ChipnetTestnetReachable
- Tip
- 327,883
- Lag
- One node reporting
- Errors
- 0.3%14 / 4,531
/healthz answers ok: 1 of 1 probed node answering.
- chipnet-node-1Preferred127.0.0.1:41235Reachable
- Tip
- 327,883
- Lag
- At tip
- Errors
- 0.3%14 / 4,531
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 Chipnet, 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
- 15,139
- Failed
- 1,697 (11.2%)
- Active now
- 0
- Slowest call
- 12 s
LiveTransactionServiceGetAddressHistoryIdleFailures100.0%Last 15 min—Average10 ms
Volume
Outcome
Timing
Payload
Active wait
LiveTransactionServiceGetAddressStatsIdleFailures100.0%Last 15 min—Average10 ms
Volume
Outcome
Timing
Payload
Active wait
LiveTransactionServiceFindSpentOutputsIdleFailures98.7%Last 15 min100.0%Average38 ms
Volume
Outcome
Timing
Payload
Active wait
BlockChainServiceGetBlockTransactionsIdleFailures5.8%Last 15 min11.4%Average199 ms
Volume
Outcome
Timing
Payload
Active wait
LiveTransactionServiceGetMempoolInfoIdleFailures1.1%Last 15 min1.2%Average19 ms
Volume
Outcome
Timing
Payload
Active wait
Show the other 11 call families
BlockChainServiceGetBlockChainInfoIdleFailures0.6%Last 15 min2.8%Average42 ms
Volume
Outcome
Timing
Payload
Active wait
BlockChainServiceGetBlockVerboseCompatIdleFailures0.3%Last 15 min0.0%Average74 ms
Volume
Outcome
Timing
Payload
Active wait
LiveTransactionServiceGetMempoolTxIdsIdleFailures0.2%Last 15 min0.0%Average47 ms
Volume
Outcome
Timing
Payload
Active wait
LiveTransactionServiceGetTransactionsIdleFailures0.1%Last 15 min2.6%Average63 ms
Volume
Outcome
Timing
Payload
Active wait
IndexerServiceGetAvailableIndexersIdleFailures0.1%Last 15 min12.5%Average28 ms
Volume
Outcome
Timing
Payload
Active wait
IndexerServiceGetBcmrMetadataIdleFailures0.0%Last 15 min0.0%Average15 ms
Volume
Outcome
Timing
Payload
Active wait
BlockChainServiceGetBlockHeaderIdleFailures0.0%Last 15 min0.0%Average10 ms
Volume
Outcome
Timing
Payload
Active wait
LiveTransactionServiceSearchCashTokenCommitmentIdleFailures0.0%Last 15 min0.0%Average10 ms
Volume
Outcome
Timing
Payload
Active wait
IndexerServiceGetIndexerLastBlockIdleFailures0.0%Last 15 min0.0%Average5 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 (199 ms). 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 | chipnet-node-1 | 127.0.0.1:41235 Pool 8/8 active Open sessions 4 to backend Busy 0 · Reserved fast 1 | Up | Ready | chip | 327,883 | — | 10 ms | 4,517 | 14 | 2026-10-14 20:01:05 UTC | 2026-10-14 20:00:57 UTC | OK · unified API reachable; index readiness not probed |
