41m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
1h 25m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
2h 5m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
2h 43m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
3h 28m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
4h 10m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
4h 59m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
5h 44m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
6h 21m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
7h 9m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
7h 49m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
8h 39m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
9h 16m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
9h 57m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
10h 45m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
11h 37m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
12h 16m |
Could not connect! |
- |
- |
- |
- |
13h 2m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
13h 45m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
14h 28m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
15h 6m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
15h 45m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
16h 26m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
17h 9m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
18h 3m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |