SiaMining


51288c34ad6b59b15e8fe9462ee6975fff83015a7ded384d5c9f7e0f719aa8751c370cee9430

Statistics

Unpaid Balance
172.17 SC
All-Time Rewards
43,652.58 SC
All-Time Hashes
32,031 PH
Blocks Found
1
Last Share
08:54:18 UTC
(just now)
Hash Rate Valid Shares Stale Shares Invalid Shares Rewards
5 min 1,569 GH/s 28,049,408 0 (0.0%) 0 (0.0%) 0.56 SC
15 min 1,344 GH/s 72,089,600 0 (0.0%) 0 (0.0%) 1.44 SC
60 min 1,156 GH/s 248,086,528 0 (0.0%) 0 (0.0%) 4.99 SC
6 hours 1,103 GH/s 1,419,476,992 524,288 (0.0%) 0 (0.0%) 28.66 SC
24 hours 1,073 GH/s 5,521,118,976 7,077,888 (0.1%) 0 (0.0%) 110.61 SC

Workers (2/2)

Last refreshed: 08:54:23 UTC (just now)

Name Last Share 5 minutes 15 minutes 1 hour 6 hours 24 hours
HSBOX_2just now
Stratum
880 GH/s
0.0% stale
748 GH/s
0.0% stale
562 GH/s
0.0% stale
538 GH/s
0.1% stale
533 GH/s
0.1% stale
HSBOX_3just now
Stratum
689 GH/s
0.0% stale
596 GH/s
0.0% stale
594 GH/s
0.0% stale
565 GH/s
0.0% stale
541 GH/s
0.2% 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-07-25 19:10 UTC 495.16 SC 8d0cd726c4499adc... confirmed
2024-07-20 19:10 UTC 500.73 SC f7db908509905bd5... confirmed
2024-07-16 03:10 UTC 500.51 SC 47f93db466f47771... confirmed
2024-07-11 15:40 UTC 500.33 SC eb844ebe1b446d24... confirmed
2024-07-07 09:40 UTC 500.25 SC 52ee20e66258e24e... confirmed
2024-07-03 00:10 UTC 500.42 SC 30fc2c5678d49699... confirmed
2024-06-28 17:10 UTC 100.88 SC 6a233b328c68c9c7... confirmed
Show more...

All-Time Paid Out: 43,480.40 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.