f6152df1edb6f61f6daa48edaf50f495224503f7d3af8925bdba0076f9fd12fd711b7e4920a0
Statistics
- Unpaid Balance
- 84.22 SC
- All-Time Rewards
- 268,230.00 SC
- All-Time Hashes
- 178,859 PH
- Blocks Found
- 12
- Last Share
- 05:59:30 UTC
(just now)
Hash Rate | Valid Shares | Stale Shares | Invalid Shares | Rewards | |
---|---|---|---|---|---|
5 min | 5,893 GH/s | 105,381,888 | 0 (0.0%) | 0 (0.0%) | 2.18 SC |
15 min | 5,717 GH/s | 306,708,480 | 0 (0.0%) | 0 (0.0%) | 6.32 SC |
60 min | 5,796 GH/s | 1,243,611,136 | 0 (0.0%) | 0 (0.0%) | 25.49 SC |
6 hours | 5,653 GH/s | 7,273,447,424 | 3,932,160 (0.1%) | 0 (0.0%) | 151.65 SC |
24 hours | 5,685 GH/s | 29,265,821,696 | 12,320,768 (0.0%) | 0 (0.0%) | 602.66 SC |
Workers (4/4)
Last refreshed: 05:59:34 UTC (just now)
Name | Last Share | 5 minutes | 15 minutes | 1 hour | 6 hours | 24 hours |
---|---|---|---|---|---|---|
Ayra1 | just now Stratum | 3,313 GH/s 0.0% stale | 3,030 GH/s 0.0% stale | 2,920 GH/s 0.0% stale | 2,915 GH/s 0.1% stale | 2,926 GH/s 0.1% stale |
Munira1 | just now Stratum | 997 GH/s 0.0% stale | 889 GH/s 0.0% stale | 980 GH/s 0.0% stale | 904 GH/s 0.1% stale | 907 GH/s 0.0% stale |
Nuha1 | just now Stratum | 968 GH/s 0.0% stale | 919 GH/s 0.0% stale | 955 GH/s 0.0% stale | 930 GH/s 0.0% stale | 936 GH/s 0.0% stale |
Taima1 | just now Stratum | 557 GH/s 0.0% stale | 821 GH/s 0.0% stale | 941 GH/s 0.0% stale | 903 GH/s 0.1% stale | 916 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: 268,145.77 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.