2m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
36m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
1h 10m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
1h 46m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
2h 22m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
3h |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
3h 46m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
4h 25m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
4h 59m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
5h 36m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
6h 17m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
6h 57m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
7h 46m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
8h 26m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
9h 3m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
9h 39m |
Could not connect! |
- |
- |
- |
- |
10h 13m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
10h 59m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
11h 39m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
12h 23m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
13h |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
13h 38m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
14h 23m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
14h 57m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
15h 42m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |