Operations · Bitcoin Cash Tempnet (experimental)
Status
Is the explorer's backend answering on Bitcoin Cash Tempnet (experimental)? The summary uses the same reachability rule as /healthz. Call details and node diagnostics follow, collapsed.
Is the stack OK?
Summary
- Bitcoin Cash Tempnet (experimental)TestnetReachable
- Tip
- 339,206
- Lag
- One node reporting
- Errors
- 0.0%2 / 22,502
/healthz answers ok: 1 of 1 probed node answering.
- tempnet-node-1Preferred127.0.0.1:51235Reachable
- Tip
- 339,206
- Lag
- At tip
- Errors
- 0.0%2 / 22,502
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 Tempnet (experimental), 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
- 17
- Completed
- 18,589
- Failed
- 2 (0.0%)
- Active now
- 0
- Slowest call
- 1 s
LiveTransactionServiceGetMempoolInfoIdleFailures0.0%Last 15 min0.0%Average0 ms
Volume
Outcome
Timing
Payload
Active wait
IndexerServiceGetBcmrMetadataIdleFailures0.0%Last 15 min—Average27 ms
Volume
Outcome
Timing
Payload
Active wait
IndexerServiceFindCashTokenCommitmentIdleFailures0.0%Last 15 min—Average22 ms
Volume
Outcome
Timing
Payload
Active wait
LiveTransactionServiceSearchCashTokenCommitmentIdleFailures0.0%Last 15 min—Average22 ms
Volume
Outcome
Timing
Payload
Active wait
IndexerServiceGetAvailableIndexersIdleFailures0.0%Last 15 min—Average3 ms
Volume
Outcome
Timing
Payload
Active wait
Show the other 12 call families
LiveTransactionServiceGetAddressHistoryIdleFailures0.0%Last 15 min—Average2 ms
Volume
Outcome
Timing
Payload
Active wait
LiveTransactionServiceGetAddressStatsIdleFailures0.0%Last 15 min—Average1 ms
Volume
Outcome
Timing
Payload
Active wait
BlockChainServiceGetBlockChainInfoIdleFailures0.0%Last 15 min0.0%Average0 ms
Volume
Outcome
Timing
Payload
Active wait
BlockChainServiceGetBlockHeaderIdleFailures0.0%Last 15 min—Average0 ms
Volume
Outcome
Timing
Payload
Active wait
BlockChainServiceGetBlockTransactionsIdleFailures0.0%Last 15 min0.0%Average0 ms
Volume
Outcome
Timing
Payload
Active wait
BlockChainServiceGetBlockVerboseCompatIdleFailures0.0%Last 15 min0.0%Average0 ms
Volume
Outcome
Timing
Payload
Active wait
IndexerServiceGetIndexerLastBlockIdleFailures0.0%Last 15 min0.0%Average0 ms
Volume
Outcome
Timing
Payload
Active wait
LiveTransactionServiceFindSpentOutputsIdleFailures0.0%Last 15 min—Average0 ms
Volume
Outcome
Timing
Payload
Active wait
LiveTransactionServiceGetMempoolTxIdsIdleFailures0.0%Last 15 min0.0%Average0 ms
Volume
Outcome
Timing
Payload
Active wait
LiveTransactionServiceGetTransactionsIdleFailures0.0%Last 15 min—Average0 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 (27 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 | tempnet-node-1 | 127.0.0.1:51235 Pool 1/1 active Open sessions 1 to backend Busy 0 · Reserved fast 0 | Up | Ready | temp | 339,206 | — | 3 ms | 22,500 | 2 | 2026-10-23 23:17:00 UTC | 2026-10-23 13:22:09 UTC | OK · unified API reachable; index readiness not probed |
