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,808
- Lag
- One node reporting
- Errors
- 0.5%250 / 54,569
/healthz answers ok: 1 of 1 probed node answering.
- chipnet-node-1Preferred127.0.0.1:41235Reachable
- Tip
- 327,808
- Lag
- At tip
- Errors
- 0.5%250 / 54,569
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. Open a row for volume, outcome, timing, payload and active-wait detail.
- Call families
- 15
- Completed
- 197,384
- Failed
- 21,544 (10.9%)
- Active now
- 0
- Slowest call
- 12 s
LiveTransactionServiceFindSpentOutputsIdleFailures97.2%Average37 ms
Volume
Outcome
Timing
Payload
Active wait
LiveTransactionServiceGetMempoolInfoIdleFailures2.4%Average34 ms
Volume
Outcome
Timing
Payload
Active wait
BlockChainServiceGetBlockChainInfoIdleFailures1.6%Average69 ms
Volume
Outcome
Timing
Payload
Active wait
BlockChainServiceGetBlockTransactionsIdleFailures1.5%Average45 ms
Volume
Outcome
Timing
Payload
Active wait
LiveTransactionServiceGetMempoolTxIdsIdleFailures0.8%Average43 ms
Volume
Outcome
Timing
Payload
Active wait
Show the other 10 call families
BlockChainServiceGetBlockVerboseCompatIdleFailures0.6%Average95 ms
Volume
Outcome
Timing
Payload
Active wait
LiveTransactionServiceGetTransactionsIdleFailures0.3%Average114 ms
Volume
Outcome
Timing
Payload
Active wait
BlockChainServiceGetBlockHeaderIdleFailures0.3%Average36 ms
Volume
Outcome
Timing
Payload
Active wait
IndexerServiceGetAvailableIndexersIdleFailures0.3%Average62 ms
Volume
Outcome
Timing
Payload
Active wait
IndexerServiceGetIndexerLastBlockIdleFailures0.0%Average29 ms
Volume
Outcome
Timing
Payload
Active wait
IndexerServiceGetBcmrMetadataIdleFailures0.0%Average13 ms
Volume
Outcome
Timing
Payload
Active wait
LiveTransactionServiceSearchCashTokenCommitmentIdleFailures0.0%Average11 ms
Volume
Outcome
Timing
Payload
Active wait
BlockChainServiceGetBlockSummariesIdleFailuresNo completed callsAverageUnavailable
Volume
Outcome
Timing
Payload
Active wait
IndexerServiceFindTransactionIdleFailuresNo completed callsAverageUnavailable
Volume
Outcome
Timing
Payload
Active wait
LiveTransactionServiceSearchMempoolIdleFailuresNo completed callsAverageUnavailable
Volume
Outcome
Timing
Payload
Active wait
Counts reset when the BlockExplorer process restarts. Failure bars run from 0 to 100%. Latency bars are relative to the slowest average (114 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 8 to backend Busy 1 · Reserved fast 1 | Up | Ready | chip | 327,808 | — | 10 ms | 54,319 | 250 | 2026-10-14 06:51:26 UTC | 2026-10-14 06:47:09 UTC | OK · unified API reachable; index readiness not probed |
