02f134fc290c4c9b33eb115653a4e053ad21a433f4d044a1a257cffa96813b0157afcf6947d5
Statistics
- Unpaid Balance
- 242.73 SC
- All-Time Rewards
- 148,672.64 SC
- All-Time Hashes
- 97,979 PH
- Blocks Found
- 5
- Last Share
- 00:16:42 UTC
(just now)
Hash Rate | Valid Shares | Stale Shares | Invalid Shares | Rewards | |
---|---|---|---|---|---|
5 min | 5,292 GH/s | 94,633,984 | 0 (0.0%) | 0 (0.0%) | 1.93 SC |
15 min | 4,928 GH/s | 264,339,456 | 0 (0.0%) | 0 (0.0%) | 5.41 SC |
60 min | 4,597 GH/s | 979,927,040 | 6,553,600 (0.7%) | 0 (0.0%) | 20.17 SC |
6 hours | 4,566 GH/s | 5,871,304,704 | 7,077,888 (0.1%) | 0 (0.0%) | 124.11 SC |
24 hours | 4,565 GH/s | 23,499,407,360 | 11,272,192 (0.0%) | 0 (0.0%) | 510.84 SC |
Workers (4/4)
Last refreshed: 00:16:48 UTC (just now)
Name | Last Share | 5 minutes | 15 minutes | 1 hour | 6 hours | 24 hours |
---|---|---|---|---|---|---|
hsbox-01 | 32 sec ago Stratum | 601 GH/s 0.0% stale | 533 GH/s 0.0% stale | 564 GH/s 0.0% stale | 530 GH/s 0.0% stale | 542 GH/s 0.0% stale |
hsbox-02 | just now Stratum | 704 GH/s 0.0% stale | 603 GH/s 0.0% stale | 509 GH/s 0.0% stale | 548 GH/s 0.0% stale | 549 GH/s 0.0% stale |
hsbox-03 | just now Stratum | 469 GH/s 0.0% stale | 479 GH/s 0.0% stale | 531 GH/s 0.2% stale | 545 GH/s 0.0% stale | 545 GH/s 0.0% stale |
hslite | just now Stratum | 3,460 GH/s 0.0% stale | 3,274 GH/s 0.0% stale | 2,993 GH/s 1.0% stale | 2,943 GH/s 0.2% stale | 2,929 GH/s 0.1% 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: 148,429.90 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.