Testnet3Testnet
Test coinsWARNING: This is Bitcoin Cash Testnet3. Coins on this network have no value. Select Bitcoin Cash Mainnet above for the real Bitcoin Cash network.
Operations

Status

Failover visibility for every configured Rapids endpoint.

Configured nodes1
Reachable1
Unavailable0
Preferred nodetestnet3-node-1

Connection pooling keeps backend requests available during busy periods. Slow routes avoid the reserved fast lane whenever more than one session is active.

RankNodeEndpointReachableCooldownChainBest heightIndexed tipLatencySuccessesFailuresLast successLast failureMessage
1testnet3-node-1127.0.0.1:11235
Pool 8/8 active
Open sessions 8 to backend
Busy 0 · Reserved fast 1
UpReadytest1,731,866—10 ms376,4725,1322026-10-11 05:36:05 UTC2026-10-11 05:35:26 UTCOK · unified API reachable; index readiness not probed
Backend requests

Call timing metrics

Since process start

This public table shows the backend calls BlockExplorer has issued on Bitcoin Cash Testnet3. Use it to spot hot call families, slow responses, failures, and requests that started but still have not completed.

Call families14
Started926,488
Completed926,488
Failures6,867
Active now0
Slowest completed12 s
Longest active—
Payload seen911.64 MiB
Largest payload3.28 MiB
Payload coverage296.5%
Success rate99.3%
Call family
BlockChainService
GetBlockHeader
Idle

Volume

Started150,848
Completed150,848
Active now0

Outcome

Successes150,722
Failures126
Completion rate100.0%
Success rate99.9%

Timing

Fastest9 ms
Average16 ms
Slowest12 s

Payload

Total29.42 MiB
Average199 B
Largest201 B
Seen for 154,619 completed calls

Active wait

StatusNo active calls
Call family
BlockChainService
GetBlockVerboseCompat
Idle

Volume

Started159,021
Completed159,021
Active now0

Outcome

Successes158,308
Failures713
Completion rate100.0%
Success rate99.6%

Timing

Fastest9 ms
Average94 ms
Slowest12 s

Payload

Total160.95 MiB
Average469 B
Largest3.28 MiB
Seen for 359,235 completed calls

Active wait

StatusNo active calls
Call family
BlockChainService
GetTransaction
Idle

Volume

Started137,197
Completed137,197
Active now0

Outcome

Successes137,195
Failures2
Completion rate100.0%
Success rate100.0%

Timing

Fastest9 ms
Average11 ms
Slowest12 s

Payload

Total454.54 MiB
Average788 B
Largest185.12 KiB
Seen for 604,406 completed calls

Active wait

StatusNo active calls
Call family
IndexerService
FindTransaction
Idle

Volume

Started137,207
Completed137,207
Active now0

Outcome

Successes137,198
Failures9
Completion rate100.0%
Success rate100.0%

Timing

Fastest9 ms
Average13 ms
Slowest12 s

Payload

Total8.48 MiB
Average14 B
Largest17 B
Seen for 607,903 completed calls

Active wait

StatusNo active calls
Call family
IndexerService
GetIndexerLastBlock
Idle

Volume

Started25,136
Completed25,136
Active now0

Outcome

Successes25,129
Failures7
Completion rate100.0%
Success rate100.0%

Timing

Fastest0 ms
Average25 ms
Slowest12 s

Payload

Total1.41 MiB
Average58 B
Largest59 B
Seen for 25,129 completed calls

Active wait

StatusNo active calls
Call family
BlockChainService
GetBlockChainInfo
Idle

Volume

Started58,647
Completed58,647
Active now0

Outcome

Successes57,587
Failures1,060
Completion rate100.0%
Success rate98.2%

Timing

Fastest0 ms
Average67 ms
Slowest10 s

Payload

Total6.69 MiB
Average121 B
Largest122 B
Seen for 57,587 completed calls

Active wait

StatusNo active calls
Call family
IndexerService
GetAvailableIndexers
Idle

Volume

Started54
Completed54
Active now0

Outcome

Successes38
Failures16
Completion rate100.0%
Success rate70.4%

Timing

Fastest10 ms
Average1 s
Slowest9 s

Payload

Total305 B
Average8 B
Largest9 B
Seen for 38 completed calls

Active wait

StatusNo active calls
Call family
LiveTransactionService
GetMempoolTxIds
Idle

Volume

Started39,644
Completed39,644
Active now0

Outcome

Successes39,491
Failures153
Completion rate100.0%
Success rate99.6%

Timing

Fastest0 ms
Average27 ms
Slowest2 s

Payload

Total2.01 MiB
Average53 B
Largest1.07 KiB
Seen for 39,491 completed calls

Active wait

StatusNo active calls
Call family
BlockChainService
GetBlock
Idle

Volume

Started144,396
Completed144,396
Active now0

Outcome

Successes144,376
Failures20
Completion rate100.0%
Success rate100.0%

Timing

Fastest9 ms
Average10 ms
Slowest1 s

Payload

Total149.39 MiB
Average1.06 KiB
Largest1,002.24 KiB
Seen for 144,376 completed calls

Active wait

StatusNo active calls
Call family
LiveTransactionService
GetMempoolInfo
Idle

Volume

Started74,304
Completed74,304
Active now0

Outcome

Successes69,543
Failures4,761
Completion rate100.0%
Success rate93.6%

Timing

Fastest0 ms
Average81 ms
Slowest1 s

Payload

Total2.31 MiB
Average34 B
Largest37 B
Seen for 69,543 completed calls

Active wait

StatusNo active calls
Call family
IndexerService
GetBcmrMetadata
Idle

Volume

Started23
Completed23
Active now0

Outcome

Successes23
Failures0
Completion rate100.0%
Success rate100.0%

Timing

Fastest10 ms
Average15 ms
Slowest50 ms

Payload

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

Active wait

StatusNo active calls
Call family
LiveTransactionService
SearchCashTokenCommitment
Idle

Volume

Started11
Completed11
Active now0

Outcome

Successes11
Failures0
Completion rate100.0%
Success rate100.0%

Timing

Fastest10 ms
Average10 ms
Slowest10 ms

Payload

Total77 B
Average7 B
Largest7 B
Seen for 11 completed calls

Active wait

StatusNo active calls
Call family
BlockChainService
GetBlockSummaries
Idle

Volume

Started0
Completed0
Active now0

Outcome

Successes0
Failures0
Completion rate—
Success rate—

Timing

Fastest—
Average—
Slowest—

Payload

Total53.94 MiB
Average2.07 KiB
Largest21.75 KiB
Seen for 26,730 completed calls

Active wait

StatusNo active calls
Call family
LiveTransactionService
SearchMempool
Idle

Volume

Started0
Completed0
Active now0

Outcome

Successes0
Failures0
Completion rate—
Success rate—

Timing

Fastest—
Average—
Slowest—

Payload

Total42.49 MiB
Average67 B
Largest4.3 KiB
Seen for 657,972 completed calls

Active wait

StatusNo active calls
Counts reset when the BlockExplorer process restarts. Payload shows observed response data where available. Active requests and oldest wait time help identify slow backend calls.