Operations · Bitcoin Cash Mainnet

Status

Is the explorer's backend answering on Bitcoin Cash Mainnet? 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 MainnetReachable
Tip
972,781
Lag
One node reporting
Errors
19.1%32,914 / 172,773
/healthz answers ok: 1 of 1 probed node answering.
mainnet-node-1Preferred127.0.0.1:1235Reachable
Tip
972,781
Lag
At tip
Errors
19.1%32,914 / 172,773
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 Mainnet, worst first: highest failure rate, then slowest average. Open a row for volume, outcome, timing, payload and active-wait detail.

Call families: 16
Completed: 552,041
Failed: 336,976 (61.0%)
Active now: 0
Slowest call: 12 s

LiveTransactionServiceGetAddressHistoryIdleFailures100.0%Average20 ms

Volume

Started261,822

Completed261,822

Active now0

Outcome

Successes0

Failures261,822

Completion rate100.0%

Success rate0.0%

Timing

Fastest9 ms

Average20 ms

Slowest12 s

Payload

StatusUnavailable

Best-effort bytes are not exposed for this call family yet.

Active wait

StatusNo active calls

LiveTransactionServiceFindSpentOutputsIdleFailures99.0%Average19 ms

Volume

Started74,898

Completed74,898

Active now0

Outcome

Successes725

Failures74,173

Completion rate100.0%

Success rate1.0%

Timing

Fastest0 ms

Average19 ms

Slowest12 s

Payload

Total8.7 KiB

Average12 B

Largest226 B

Seen for 725 completed calls

Active wait

StatusNo active calls

BlockChainServiceGetBlockTransactionsIdleFailures1.5%Average47 ms

Volume

Started35,472

Completed35,472

Active now0

Outcome

Successes34,926

Failures546

Completion rate100.0%

Success rate98.5%

Timing

Fastest10 ms

Average47 ms

Slowest1 s

Payload

Total418.75 MiB

Average12.28 KiB

Largest30.89 KiB

Seen for 34,926 completed calls

Active wait

StatusNo active calls

LiveTransactionServiceGetMempoolInfoIdleFailures1.3%Average21 ms

Volume

Started11,237

Completed11,237

Active now0

Outcome

Successes11,092

Failures145

Completion rate100.0%

Success rate98.7%

Timing

Fastest0 ms

Average21 ms

Slowest1 s

Payload

Total406.94 KiB

Average37 B

Largest41 B

Seen for 11,092 completed calls

Active wait

StatusNo active calls

IndexerServiceGetAvailableIndexersIdleFailures0.5%Average92 ms

Volume

Started1,300

Completed1,300

Active now0

Outcome

Successes1,293

Failures7

Completion rate100.0%

Success rate99.5%

Timing

Fastest10 ms

Average92 ms

Slowest12 s

Payload

Total10.33 KiB

Average8 B

Largest9 B

Seen for 1,293 completed calls

Active wait

StatusNo active calls

Show the other 11 call families

BlockChainServiceGetBlockChainInfoIdleFailures0.5%Average31 ms

Volume

Started10,168

Completed10,168

Active now0

Outcome

Successes10,118

Failures50

Completion rate100.0%

Success rate99.5%

Timing

Fastest0 ms

Average31 ms

Slowest3 s

Payload

Total1.17 MiB

Average121 B

Largest122 B

Seen for 10,118 completed calls

Active wait

StatusNo active calls

BlockChainServiceGetBlockHeaderIdleFailures0.3%Average32 ms

Volume

Started6,126

Completed6,126

Active now0

Outcome

Successes6,110

Failures16

Completion rate100.0%

Success rate99.7%

Timing

Fastest10 ms

Average32 ms

Slowest12 s

Payload

Total1.31 MiB

Average197 B

Largest201 B

Seen for 6,976 completed calls

Active wait

StatusNo active calls

LiveTransactionServiceGetTransactionsIdleFailures0.2%Average67 ms

Volume

Started75,097

Completed75,097

Active now0

Outcome

Successes74,942

Failures155

Completion rate100.0%

Success rate99.8%

Timing

Fastest10 ms

Average67 ms

Slowest12 s

Payload

Total882.39 MiB

Average6.12 KiB

Largest1.16 MiB

Seen for 147,653 completed calls

Active wait

StatusNo active calls

BlockChainServiceGetBlockVerboseCompatIdleFailures0.2%Average67 ms

Volume

Started30,059

Completed30,059

Active now0

Outcome

Successes30,004

Failures55

Completion rate100.0%

Success rate99.8%

Timing

Fastest9 ms

Average67 ms

Slowest12 s

Payload

Total593.3 MiB

Average10.62 KiB

Largest1.67 MiB

Seen for 57,222 completed calls

Active wait

StatusNo active calls

LiveTransactionServiceGetMempoolTxIdsIdleFailures0.2%Average33 ms

Volume

Started4,323

Completed4,323

Active now0

Outcome

Successes4,316

Failures7

Completion rate100.0%

Success rate99.8%

Timing

Fastest0 ms

Average33 ms

Slowest2 s

Payload

Total43.96 MiB

Average10.43 KiB

Largest343.35 KiB

Seen for 4,316 completed calls

Active wait

StatusNo active calls

IndexerServiceGetBcmrMetadataIdleFailures0.0%Average22 ms

Volume

Started35,990

Completed35,990

Active now0

Outcome

Successes35,990

Failures0

Completion rate100.0%

Success rate100.0%

Timing

Fastest0 ms

Average22 ms

Slowest1 s

Payload

StatusUnavailable

Best-effort bytes are not exposed for this call family yet.

Active wait

StatusNo active calls

LiveTransactionServiceSearchCashTokenCommitmentIdleFailures0.0%Average20 ms

Volume

Started1,256

Completed1,256

Active now0

Outcome

Successes1,256

Failures0

Completion rate100.0%

Success rate100.0%

Timing

Fastest10 ms

Average20 ms

Slowest11 s

Payload

Total8.75 KiB

Average7 B

Largest8 B

Seen for 1,247 completed calls

Active wait

StatusNo active calls

IndexerServiceGetIndexerLastBlockIdleFailures0.0%Average13 ms

Volume

Started4,293

Completed4,293

Active now0

Outcome

Successes4,293

Failures0

Completion rate100.0%

Success rate100.0%

Timing

Fastest0 ms

Average13 ms

Slowest11 s

Payload

Total246.5 KiB

Average58 B

Largest59 B

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

Total14.1 MiB

Average3.01 KiB

Largest21.47 KiB

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

Total33 B

Average11 B

Largest11 B

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

Total81.95 MiB

Average1,023 B

Largest303.81 KiB

Seen for 83,997 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 (92 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	mainnet-node-1 Inspect node	127.0.0.1:1235 Pool 8/8 active Open sessions 8 to backend Busy 1 · Reserved fast 1	Up	Ready	main	972,781	—	10 ms	139,859	32,914	2026-10-14 05:56:26 UTC	2026-10-14 05:56:22 UTC	OK · unified API reachable; index readiness not probed