dd24c972217171d5396503377b5ce38d0c647bc3d86553ab3ba57d81504a23ab9f1d6e240ed0
Statistics
- Unpaid Balance
- 229.38 SC
- All-Time Rewards
- 135,414.22 SC
- All-Time Hashes
- 95,807 PH
- Blocks Found
- 5
- Last Share
- 14:14:42 UTC
(just now)
| Hash Rate | Valid Shares | Stale Shares | Invalid Shares | Rewards | |
|---|---|---|---|---|---|
| 5 min | 2,126 GH/s | 38,010,880 | 0 (0.0%) | 0 (0.0%) | 0.61 SC |
| 15 min | 2,073 GH/s | 111,214,592 | 0 (0.0%) | 0 (0.0%) | 1.79 SC |
| 60 min | 2,016 GH/s | 432,504,832 | 0 (0.0%) | 0 (0.0%) | 6.91 SC |
| 6 hours | 1,932 GH/s | 2,485,747,712 | 1,310,720 (0.1%) | 0 (0.0%) | 39.90 SC |
| 24 hours | 1,847 GH/s | 9,507,864,576 | 3,538,944 (0.0%) | 1,572,864 (0.0%) | 155.66 SC |
Workers (4/4)
Last refreshed: 14:14:51 UTC (just now)
| Name | Last Share | 5 minutes | 15 minutes | 1 hour | 6 hours | 24 hours |
|---|---|---|---|---|---|---|
| HS-1 | just now Stratum | 572 GH/s 0.0% stale | 534 GH/s 0.0% stale | 525 GH/s 0.0% stale | 481 GH/s 0.1% stale | 466 GH/s 0.0% stale |
| HS-2 | just now Stratum | 498 GH/s 0.0% stale | 523 GH/s 0.0% stale | 528 GH/s 0.0% stale | 485 GH/s 0.0% stale | 465 GH/s 0.0% stale |
| HS-3 | 33 sec ago Stratum | 396 GH/s 0.0% stale | 474 GH/s 0.0% stale | 470 GH/s 0.0% stale | 484 GH/s 0.0% stale | 457 GH/s 0.0% stale |
| HS-4 | just now Stratum | 660 GH/s 0.0% stale | 538 GH/s 0.0% stale | 492 GH/s 0.0% stale | 481 GH/s 0.0% stale | 458 GH/s 0.0% stale |
Recent Payouts
Reminder: Due to Sia's Foundation hardfork, you must upgrade your Sia wallet software to version 1.5.4 or higher. You can continue to use the same address for mining, and no changes to your configuration are needed. For more information about the fork, click here.
Payouts are performed daily with a threshold of 500 SC, or up to every 6 hours when over 1000 SC.
All-Time Paid Out: 135,184.84 SC
Note: If you have not received one of the payout transactions listed above, please click on the transaction ID to look it up on the Explorer. If the transaction appears there, it is proof that it went through successfully, and that the problem is with the receiving end. If you are using an exchange address, you should contact the exchange.