| 34m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 1h 38m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 2h 22m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 3h 9m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 3h 55m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 4h 42m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 5h 32m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 6h 17m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 7h 12m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 7h 54m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 8h 45m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 9h 26m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 10h 18m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 10h 59m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 11h 43m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 12h 28m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 13h 16m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 14h 3m |
Could not connect! |
- |
- |
- |
- |
| 14h 49m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 15h 33m |
Could not connect! |
- |
- |
- |
- |
| 16h 20m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 17h 20m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 18h 11m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 18h 57m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 19h 43m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |