| 42m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 1h 34m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 2h 17m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 3h 5m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 3h 58m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 4h 43m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 5h 31m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 6h 24m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 7h 6m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 7h 49m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 8h 40m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 9h 26m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 10h 11m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 10h 52m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 11h 33m |
Could not connect! |
- |
- |
- |
- |
| 12h 17m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 13h |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 13h 47m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 14h 32m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 15h 15m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 16h 2m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 16h 52m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 17h 37m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 18h 27m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 19h 15m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |