| 8m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 1h 2m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 1h 54m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 2h 35m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 3h 24m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 4h 13m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 5h 1m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 5h 48m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 6h 31m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 7h 14m |
Could not connect! |
- |
- |
- |
- |
| 7h 57m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 8h 44m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 9h 29m |
Could not connect! |
- |
- |
- |
- |
| 10h 17m |
Could not connect! |
- |
- |
- |
- |
| 11h |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 11h 44m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 12h 30m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 13h 17m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 14h 2m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 14h 44m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 15h 28m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 16h 16m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 17h 12m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 17h 54m |
Could not connect! |
- |
- |
- |
- |
| 18h 37m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |