| 35m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 1h 30m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 2h 15m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 2h 55m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 3h 33m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 4h 21m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 4h 57m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 5h 35m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 6h 22m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 7h |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 7h 51m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 8h 36m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 9h 23m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 10h 8m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 10h 44m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 11h 24m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 12h 3m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 12h 40m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 13h 22m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 14h 13m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 14h 52m |
Could not connect! |
- |
- |
- |
- |
| 15h 28m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 16h 16m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 16h 58m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 17h 34m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |