| 39m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 1h 19m |
Could not connect! |
- |
- |
- |
- |
| 2h 1m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 2h 45m |
Could not connect! |
- |
- |
- |
- |
| 3h 28m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 4h 13m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 4h 53m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 5h 34m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 6h 23m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 7h 4m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 7h 48m |
Could not connect! |
- |
- |
- |
- |
| 8h 32m |
Could not connect! |
- |
- |
- |
- |
| 9h 18m |
Could not connect! |
- |
- |
- |
- |
| 9h 53m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 10h 43m |
Could not connect! |
- |
- |
- |
- |
| 11h 28m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 12h 11m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 12h 58m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 13h 40m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 14h 19m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 15h |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 15h 40m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 16h 26m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 17h 15m |
Could not connect! |
- |
- |
- |
- |
| 18h 2m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |