Operations · Bitcoin Cash Testnet4

Status

Is the explorer's backend answering on Bitcoin Cash Testnet4? The summary uses the same reachability rule as /healthz. Call details and node diagnostics follow, collapsed.

Is the stack OK?

Summary

Errors since process start

Bitcoin Cash Testnet4TestnetReachable
Tip
327,788
Lag
One node reporting
Errors
2.4%286 / 12,078
/healthz answers ok: 1 of 1 probed node answering.
testnet4-node-1Preferred127.0.0.1:21235Reachable
Tip
327,788
Lag
At tip
Errors
2.4%286 / 12,078
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

Since process start

Every backend call family the explorer has issued on Bitcoin Cash Testnet4, worst first: highest failure rate, then slowest average. Open a row for volume, outcome, timing, payload and active-wait detail.

Call families: 15
Completed: 75,246
Failed: 583 (0.8%)
Active now: 0
Slowest call: 12 s

IndexerServiceGetAvailableIndexersIdleFailures12.5%Average329 ms

Volume

Started8

Completed8

Active now0

Outcome

Successes7

Failures1

Completion rate100.0%

Success rate87.5%

Timing

Fastest10 ms

Average329 ms

Slowest2 s

Payload

Total56 B

Average8 B

Largest8 B

Seen for 7 completed calls

Active wait

StatusNo active calls

LiveTransactionServiceFindSpentOutputsIdleFailures6.1%Average10 ms

Volume

Started66

Completed66

Active now0

Outcome

Successes62

Failures4

Completion rate100.0%

Success rate93.9%

Timing

Fastest10 ms

Average10 ms

Slowest30 ms

Payload

Total1.5 KiB

Average24 B

Largest38 B

Seen for 62 completed calls

Active wait

StatusNo active calls

BlockChainServiceGetBlockVerboseCompatIdleFailures3.3%Average277 ms

Volume

Started332

Completed332

Active now0

Outcome

Successes321

Failures11

Completion rate100.0%

Success rate96.7%

Timing

Fastest10 ms

Average277 ms

Slowest11 s

Payload

Total9.2 MiB

Average270 B

Largest309 B

Seen for 35,720 completed calls

Active wait

StatusNo active calls

LiveTransactionServiceGetMempoolInfoIdleFailures3.0%Average41 ms

Volume

Started11,622

Completed11,622

Active now0

Outcome

Successes11,272

Failures350

Completion rate100.0%

Success rate97.0%

Timing

Fastest0 ms

Average41 ms

Slowest1 s

Payload

Total367.82 KiB

Average33 B

Largest36 B

Seen for 11,272 completed calls

Active wait

StatusNo active calls

BlockChainServiceGetBlockChainInfoIdleFailures1.7%Average84 ms

Volume

Started10,025

Completed10,025

Active now0

Outcome

Successes9,854

Failures171

Completion rate100.0%

Success rate98.3%

Timing

Fastest0 ms

Average84 ms

Slowest3 s

Payload

Total1.15 MiB

Average122 B

Largest123 B

Seen for 9,854 completed calls

Active wait

StatusNo active calls

Show the other 10 call families

BlockChainServiceGetBlockHeaderIdleFailures0.9%Average10 ms

Volume

Started548

Completed548

Active now0

Outcome

Successes543

Failures5

Completion rate100.0%

Success rate99.1%

Timing

Fastest10 ms

Average10 ms

Slowest43 ms

Payload

Total256.2 KiB

Average186 B

Largest200 B

Seen for 1,409 completed calls

Active wait

StatusNo active calls

LiveTransactionServiceGetMempoolTxIdsIdleFailures0.3%Average21 ms

Volume

Started12,561

Completed12,561

Active now0

Outcome

Successes12,524

Failures37

Completion rate100.0%

Success rate99.7%

Timing

Fastest0 ms

Average21 ms

Slowest2 s

Payload

Total105.35 KiB

Average8 B

Largest42 B

Seen for 12,524 completed calls

Active wait

StatusNo active calls

IndexerServiceGetIndexerLastBlockIdleFailures0.0%Average34 ms

Volume

Started4,429

Completed4,429

Active now0

Outcome

Successes4,427

Failures2

Completion rate100.0%

Success rate100.0%

Timing

Fastest0 ms

Average34 ms

Slowest12 s

Payload

Total253.31 KiB

Average58 B

Largest59 B

Seen for 4,427 completed calls

Active wait

StatusNo active calls

BlockChainServiceGetBlockTransactionsIdleFailures0.0%Average11 ms

Volume

Started35,587

Completed35,587

Active now0

Outcome

Successes35,585

Failures2

Completion rate100.0%

Success rate100.0%

Timing

Fastest0 ms

Average11 ms

Slowest1 s

Payload

Total4.96 MiB

Average146 B

Largest216 B

Seen for 35,585 completed calls

Active wait

StatusNo active calls

LiveTransactionServiceGetTransactionsIdleFailures0.0%Average137 ms

Volume

Started66

Completed66

Active now0

Outcome

Successes66

Failures0

Completion rate100.0%

Success rate100.0%

Timing

Fastest10 ms

Average137 ms

Slowest2 s

Payload

Total23.43 KiB

Average337 B

Largest471 B

Seen for 71 completed calls

Active wait

StatusNo active calls

LiveTransactionServiceSearchCashTokenCommitmentIdleFailures0.0%Average10 ms

Volume

Started2

Completed2

Active now0

Outcome

Successes2

Failures0

Completion rate100.0%

Success rate100.0%

Timing

Fastest10 ms

Average10 ms

Slowest10 ms

Payload

Total14 B

Average7 B

Largest7 B

Seen for 2 completed calls

Active wait

StatusNo active calls

BlockChainServiceGetBlockSummariesIdleFailuresNo completed callsAverageUnavailable

Volume

Started0

Completed0

Active now0

Outcome

Successes0

Failures0

Completion rate—

Success rate—

Timing

Fastest—

Average—

Slowest—

Payload

Total5.03 MiB

Average1.17 KiB

Largest13.13 KiB

Seen for 4,419 completed calls

Active wait

StatusNo active calls

BlockChainServiceGetTransactionIdleFailuresNo completed callsAverageUnavailable

Volume

Started0

Completed0

Active now0

Outcome

Successes0

Failures0

Completion rate—

Success rate—

Timing

Fastest—

Average—

Slowest—

Payload

Total85.78 KiB

Average844 B

Largest1.56 KiB

Seen for 104 completed calls

Active wait

StatusNo active calls

IndexerServiceFindTransactionIdleFailuresNo completed callsAverageUnavailable

Volume

Started0

Completed0

Active now0

Outcome

Successes0

Failures0

Completion rate—

Success rate—

Timing

Fastest—

Average—

Slowest—

Payload

Total1.4 KiB

Average13 B

Largest14 B

Seen for 106 completed calls

Active wait

StatusNo active calls

LiveTransactionServiceSearchMempoolIdleFailuresNo completed callsAverageUnavailable

Volume

Started0

Completed0

Active now0

Outcome

Successes0

Failures0

Completion rate—

Success rate—

Timing

Fastest—

Average—

Slowest—

Payload

Total367.1 KiB

Average796 B

Largest3.89 KiB

Seen for 472 completed calls

Active wait

StatusNo active calls

Counts reset when the BlockExplorer process restarts. Failure bars run from 0 to 100%. Latency bars are relative to the slowest average (329 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	testnet4-node-1 Inspect node	127.0.0.1:21235 Pool 8/8 active Open sessions 7 to backend Busy 0 · Reserved fast 1	Up	Ready	test4	327,788	—	10 ms	11,792	286	2026-10-14 06:51:26 UTC	2026-10-14 06:41:50 UTC	OK · unified API reachable; index readiness not probed