aa4d2b5f3a9d884e07c1ffeb2e12421ff3ed9d3d89c6101f25d137e390e8ba13ba66d8aa3904
Statistics
- Unpaid Balance
- 149.47 SC
- All-Time Rewards
- 993,018.67 SC
- All-Time Hashes
- 399,220 PH
- Blocks Found
- 22
- Last Share
- 02:44:04 UTC
(just now)
| Hash Rate | Valid Shares | Stale Shares | Invalid Shares | Rewards | |
|---|---|---|---|---|---|
| 5 min | 9,470 GH/s | 169,345,024 | 0 (0.0%) | 0 (0.0%) | 7.20 SC |
| 15 min | 9,500 GH/s | 509,607,936 | 0 (0.0%) | 0 (0.0%) | 21.67 SC |
| 60 min | 8,958 GH/s | 1,922,236,416 | 0 (0.0%) | 0 (0.0%) | 81.96 SC |
| 6 hours | 8,897 GH/s | 11,452,416,000 | 1,572,864 (0.0%) | 0 (0.0%) | 492.07 SC |
| 24 hours | 5,747 GH/s | 29,590,421,504 | 5,767,168 (0.0%) | 3,932,160 (0.0%) | 1,306.53 SC |
Workers (4/4)
Last refreshed: 02:44:08 UTC (just now)
| Name | Last Share | 5 minutes | 15 minutes | 1 hour | 6 hours | 24 hours |
|---|---|---|---|---|---|---|
| box1 | just now Stratum | 880 GH/s 0.0% stale | 928 GH/s 0.0% stale | 904 GH/s 0.0% stale | 911 GH/s 0.0% stale | – |
| box2 | just now Stratum | 1,026 GH/s 0.0% stale | 919 GH/s 0.0% stale | 890 GH/s 0.0% stale | 936 GH/s 0.0% stale | – |
| ibe2 | just now Stratum | 2,668 GH/s 0.0% stale | 2,903 GH/s 0.0% stale | 2,888 GH/s 0.0% stale | 2,893 GH/s 0.0% stale | 2,892 GH/s 0.0% stale |
| ibe3 | just now Stratum | 4,750 GH/s 0.0% stale | 4,476 GH/s 0.0% stale | 4,276 GH/s 0.0% stale | 4,157 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: 992,869.20 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.