| 43m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 1h 24m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 2h 13m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 3h 2m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 3h 50m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 4h 37m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 5h 20m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 6h 3m |
Could not connect! |
- |
- |
- |
- |
| 6h 46m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 7h 33m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 8h 18m |
Could not connect! |
- |
- |
- |
- |
| 9h 6m |
Could not connect! |
- |
- |
- |
- |
| 9h 49m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 10h 33m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 11h 19m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 12h 6m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 12h 50m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 13h 33m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 14h 17m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 15h 5m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 16h 1m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 16h 43m |
Could not connect! |
- |
- |
- |
- |
| 17h 26m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 18h 8m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 18h 55m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |