88f0d7939876d54ee1b337e792dc1931dd6cd7958e283b52ad1cdadc4e3465b073965f6a7974
Statistics
- Unpaid Balance
- 559.75 SC
- All-Time Rewards
- 91,484.43 SC
- All-Time Hashes
- 74,017 PH
- Blocks Found
- 3
- Last Share
- 06:43:43 UTC
(just now)
| Hash Rate | Valid Shares | Stale Shares | Invalid Shares | Rewards | |
|---|---|---|---|---|---|
| 5 min | 9,148 GH/s | 163,577,856 | 0 (0.0%) | 0 (0.0%) | 3.31 SC |
| 15 min | 9,725 GH/s | 521,666,560 | 0 (0.0%) | 0 (0.0%) | 10.59 SC |
| 60 min | 9,738 GH/s | 2,088,960,000 | 524,288 (0.0%) | 0 (0.0%) | 42.32 SC |
| 6 hours | 9,658 GH/s | 12,433,227,776 | 1,572,864 (0.0%) | 0 (0.0%) | 250.56 SC |
| 24 hours | 11.7 TH/s | 60,304,582,912 | 12,595,200 (0.0%) | 1,572,864 (0.0%) | 1,206.58 SC |
Workers (3/4)
Last refreshed: 06:43:48 UTC (just now)
| Name | Last Share | 5 minutes | 15 minutes | 1 hour | 6 hours | 24 hours |
|---|---|---|---|---|---|---|
| hsbox2 | 33 sec ago Stratum | 909 GH/s 0.0% stale | 899 GH/s 0.0% stale | 932 GH/s 0.3% stale | 926 GH/s 0.0% stale | 915 GH/s 0.0% stale |
| sclite1 | just now Stratum | 3,900 GH/s 0.0% stale | 4,271 GH/s 0.0% stale | 4,349 GH/s 0.0% stale | 4,381 GH/s 0.0% stale | 4,470 GH/s 0.0% stale |
| sclite2 | 6 hours ago Stratum | – | – | – | 13.0 GH/s 0.0% stale | 1,924 GH/s 0.0% stale |
| sclite3 | just now Stratum | 4,134 GH/s 0.0% stale | 4,525 GH/s 0.0% stale | 4,457 GH/s 0.0% stale | 4,339 GH/s 0.0% stale | 4,403 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: 90,924.67 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.