Operations · Bitcoin Cash Testnet3

Status

Is the explorer's backend answering on Bitcoin Cash Testnet3? 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 Testnet3TestnetReachable
Tip
1,732,332
Lag
One node reporting
Errors
1.5%339 / 22,842
/healthz answers ok: 1 of 1 probed node answering.
testnet3-node-1Preferred127.0.0.1:11235Reachable
Tip
1,732,332
Lag
At tip
Errors
1.5%339 / 22,842
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 Testnet3, worst first: highest failure rate, then slowest average. Open a row for volume, outcome, timing, payload and active-wait detail.

Call families: 14
Completed: 70,815
Failed: 3,915 (5.5%)
Active now: 0
Slowest call: 12 s

LiveTransactionServiceFindSpentOutputsIdleFailures74.7%Average10 ms

Volume

Started4,445

Completed4,445

Active now0

Outcome

Successes1,123

Failures3,322

Completion rate100.0%

Success rate25.3%

Timing

Fastest10 ms

Average10 ms

Slowest260 ms

Payload

Total12.67 KiB

Average11 B

Largest91 B

Seen for 1,123 completed calls

Active wait

StatusNo active calls

LiveTransactionServiceGetMempoolInfoIdleFailures3.0%Average41 ms

Volume

Started11,590

Completed11,590

Active now0

Outcome

Successes11,241

Failures349

Completion rate100.0%

Success rate97.0%

Timing

Fastest0 ms

Average41 ms

Slowest1 s

Payload

Total382.84 KiB

Average34 B

Largest37 B

Seen for 11,241 completed calls

Active wait

StatusNo active calls

BlockChainServiceGetBlockChainInfoIdleFailures1.4%Average68 ms

Volume

Started10,038

Completed10,038

Active now0

Outcome

Successes9,895

Failures143

Completion rate100.0%

Success rate98.6%

Timing

Fastest0 ms

Average68 ms

Slowest3 s

Payload

Total1.15 MiB

Average121 B

Largest122 B

Seen for 9,895 completed calls

Active wait

StatusNo active calls

BlockChainServiceGetBlockVerboseCompatIdleFailures0.7%Average144 ms

Volume

Started6,510

Completed6,510

Active now0

Outcome

Successes6,466

Failures44

Completion rate100.0%

Success rate99.3%

Timing

Fastest10 ms

Average144 ms

Slowest11 s

Payload

Total25.45 MiB

Average639 B

Largest1.28 MiB

Seen for 41,714 completed calls

Active wait

StatusNo active calls

LiveTransactionServiceGetTransactionsIdleFailures0.5%Average143 ms

Volume

Started4,469

Completed4,469

Active now0

Outcome

Successes4,445

Failures24

Completion rate100.0%

Success rate99.5%

Timing

Fastest10 ms

Average143 ms

Slowest12 s

Payload

Total8.06 MiB

Average1.08 KiB

Largest1.03 MiB

Seen for 7,625 completed calls

Active wait

StatusNo active calls

Show the other 9 call families

BlockChainServiceGetBlockHeaderIdleFailures0.4%Average32 ms

Volume

Started1,148

Completed1,148

Active now0

Outcome

Successes1,143

Failures5

Completion rate100.0%

Success rate99.6%

Timing

Fastest10 ms

Average32 ms

Slowest12 s

Payload

Total457.29 KiB

Average191 B

Largest201 B

Seen for 2,442 completed calls

Active wait

StatusNo active calls

LiveTransactionServiceGetMempoolTxIdsIdleFailures0.4%Average30 ms

Volume

Started6,125

Completed6,125

Active now0

Outcome

Successes6,100

Failures25

Completion rate100.0%

Success rate99.6%

Timing

Fastest0 ms

Average30 ms

Slowest2 s

Payload

Total402.11 KiB

Average67 B

Largest348 B

Seen for 6,100 completed calls

Active wait

StatusNo active calls

BlockChainServiceGetBlockTransactionsIdleFailures0.0%Average12 ms

Volume

Started22,053

Completed22,053

Active now0

Outcome

Successes22,050

Failures3

Completion rate100.0%

Success rate100.0%

Timing

Fastest0 ms

Average12 ms

Slowest1 s

Payload

Total6.91 MiB

Average328 B

Largest29.5 KiB

Seen for 22,050 completed calls

Active wait

StatusNo active calls

IndexerServiceGetAvailableIndexersIdleFailures0.0%Average139 ms

Volume

Started10

Completed10

Active now0

Outcome

Successes10

Failures0

Completion rate100.0%

Success rate100.0%

Timing

Fastest10 ms

Average139 ms

Slowest1 s

Payload

Total81 B

Average8 B

Largest9 B

Seen for 10 completed calls

Active wait

StatusNo active calls

IndexerServiceGetIndexerLastBlockIdleFailures0.0%Average24 ms

Volume

Started4,419

Completed4,419

Active now0

Outcome

Successes4,419

Failures0

Completion rate100.0%

Success rate100.0%

Timing

Fastest0 ms

Average24 ms

Slowest8 s

Payload

Total252.79 KiB

Average58 B

Largest59 B

Seen for 4,419 completed calls

Active wait

StatusNo active calls

LiveTransactionServiceSearchCashTokenCommitmentIdleFailures0.0%Average10 ms

Volume

Started8

Completed8

Active now0

Outcome

Successes8

Failures0

Completion rate100.0%

Success rate100.0%

Timing

Fastest10 ms

Average10 ms

Slowest10 ms

Payload

Total57 B

Average7 B

Largest8 B

Seen for 8 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.44 MiB

Average1.25 KiB

Largest21 KiB

Seen for 4,466 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

Total55 B

Average11 B

Largest11 B

Seen for 5 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

Total7.34 MiB

Average709 B

Largest2.87 KiB

Seen for 10,840 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 (144 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	testnet3-node-1 Inspect node	127.0.0.1:11235 Pool 8/8 active Open sessions 5 to backend Busy 0 · Reserved fast 1	Up	Ready	test	1,732,332	—	10 ms	22,503	339	2026-10-14 06:46:53 UTC	2026-10-14 06:32:45 UTC	OK · unified API reachable; index readiness not probed