SiaMining


51288c34ad6b59b15e8fe9462ee6975fff83015a7ded384d5c9f7e0f719aa8751c370cee9430

Statistics

Unpaid Balance
37.15 SC
All-Time Rewards
54,514.30 SC
All-Time Hashes
41,714 PH
Blocks Found
1
Last Share
12:24:34 UTC
(just now)
Hash Rate Valid Shares Stale Shares Invalid Shares Rewards
5 min 982 GH/s 17,563,648 0 (0.0%) 0 (0.0%) 0.33 SC
15 min 961 GH/s 51,281,920 262,144 (0.5%) 0 (0.0%) 0.98 SC
60 min 1,083 GH/s 232,161,280 262,144 (0.1%) 0 (0.0%) 4.48 SC
6 hours 1,091 GH/s 1,404,534,784 0 (0.0%) 0 (0.0%) 27.25 SC
24 hours 1,084 GH/s 5,580,587,008 786,432 (0.0%) 0 (0.0%) 106.30 SC

Workers (2/2)

Last refreshed: 12:24:50 UTC (just now)

Name Last Share 5 minutes 15 minutes 1 hour 6 hours 24 hours
HSBOX_2just now
Stratum
528 GH/s
0.0% stale
472 GH/s
0.0% stale
534 GH/s
0.0% stale
554 GH/s
0.0% stale
542 GH/s
0.0% stale
HSBOX_3just now
Stratum
454 GH/s
0.0% stale
469 GH/s
1.0% stale
549 GH/s
0.2% stale
537 GH/s
0.0% stale
542 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
2024-10-22 04:10 UTC 500.28 SC 733504d3c5bf9c76... confirmed
2024-10-17 06:10 UTC 500.64 SC 76bd00681b9fe13e... confirmed
2024-10-12 22:25 UTC 500.55 SC 237593011bd94071... confirmed
2024-10-09 00:10 UTC 500.68 SC 82886cc5ae31931c... confirmed
2024-10-04 05:10 UTC 500.62 SC 1129c1bbe251ae05... confirmed
2024-09-30 01:10 UTC 500.18 SC c2d624aa3af51d52... confirmed
2024-09-25 12:10 UTC 500.64 SC 46ac799baf96b1a4... confirmed
Show more...

All-Time Paid Out: 54,477.15 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.