25m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
54m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
1h 36m |
Could not connect! |
- |
- |
- |
- |
2h 13m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
2h 43m |
Could not connect! |
- |
- |
- |
- |
3h 18m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
4h 3m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
4h 38m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
5h 10m |
Could not connect! |
- |
- |
- |
- |
5h 54m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
6h 28m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
7h 1m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
7h 47m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
8h 25m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
8h 59m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
9h 46m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
10h 25m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
11h 17m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
11h 59m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
12h 33m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
13h 9m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
13h 46m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
14h 16m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
14h 48m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
15h 40m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |