SiaMining


06be758b464e101a5a6eae0b9a7d5a494f8fb66c4e479fb8a65fbf34a301c73473abe14823cf

Statistics

Unpaid Balance
309.44 SC
All-Time Rewards
16,718.28 SC
All-Time Hashes
4,182 PH
Blocks Found
1
Last Share
21:02:59 UTC
(just now)
Hash Rate Valid Shares Stale Shares Invalid Shares Rewards
5 min 440 GH/s 7,864,320 0 (0.0%) 0 (0.0%) 0.40 SC
15 min 508 GH/s 27,262,976 0 (0.0%) 0 (0.0%) 1.39 SC
60 min 539 GH/s 115,605,504 0 (0.0%) 1,310,720 (1.1%) 5.90 SC
6 hours 520 GH/s 669,777,920 0 (0.0%) 3,145,728 (0.5%) 34.03 SC
24 hours 488 GH/s 2,510,815,232 262,144 (0.0%) 8,650,752 (0.3%) 125.92 SC

Workers (1/1)

Last refreshed: 21:03:02 UTC (just now)

Name Last Share 5 minutes 15 minutes 1 hour 6 hours 24 hours
worker2just now
Stratum
440 GH/s
0.0% stale
508 GH/s
0.0% stale
539 GH/s
1.1% invalid
520 GH/s
0.0% stale
488 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.

Date/TimeAmountTransaction IDStatus
2021-05-10 10:40 UTC 500.21 SC d49efad8538110eb... confirmed
2021-05-07 07:25 UTC 501.72 SC 2a83326730ce9451... confirmed
2021-05-04 15:25 UTC 500.48 SC 1bcbd738e40c6507... confirmed
2021-05-01 03:10 UTC 500.86 SC 0916aa3a84cedd55... confirmed
2021-04-27 18:55 UTC 500.55 SC c99b7c5fc3514cd6... confirmed
2021-04-23 22:25 UTC 501.29 SC ccd25438b40a5ff5... confirmed
2021-04-20 13:55 UTC 500.86 SC e16299ff65c1dc4f... confirmed
2021-04-17 06:10 UTC 501.29 SC 2e0e998e4c46f097... confirmed
2021-04-13 21:40 UTC 500.96 SC 1d744dd266ff533f... confirmed
Show more...

All-Time Paid Out: 16,408.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.