SiaMining


f781e5597c98b113cfae007eb721c2097e2c4c4e71ae33c13275cfff45860b9a92edabbeeaf0

Statistics

Unpaid Balance
201.94 SC
All-Time Rewards
46,511.42 SC
All-Time Hashes
29,744 PH
Blocks Found
4
Last Share
05:48:34 UTC
(just now)
Hash Rate Valid Shares Stale Shares Invalid Shares Rewards
5 min 1,305 GH/s 23,330,816 0 (0.0%) 0 (0.0%) 0.44 SC
15 min 1,231 GH/s 66,060,288 0 (0.0%) 0 (0.0%) 1.25 SC
60 min 1,093 GH/s 234,618,880 0 (0.0%) 0 (0.0%) 4.47 SC
6 hours 1,074 GH/s 1,382,776,832 0 (0.0%) 0 (0.0%) 26.16 SC
24 hours 1,082 GH/s 5,571,903,488 524,288 (0.0%) 0 (0.0%) 108.57 SC

Workers (2/2)

Last refreshed: 05:48:46 UTC (just now)

Name Last Share 5 minutes 15 minutes 1 hour 6 hours 24 hours
Boxie01just now
Stratum
586 GH/s
0.0% stale
635 GH/s
0.0% stale
562 GH/s
0.0% stale
532 GH/s
0.0% stale
536 GH/s
0.0% stale
Boxie02just now
Stratum
718 GH/s
0.0% stale
596 GH/s
0.0% stale
531 GH/s
0.0% stale
542 GH/s
0.0% stale
546 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-05-17 10:10 UTC 500.20 SC e46e527a2fabf9a6... confirmed
2024-05-13 10:55 UTC 501.28 SC df5e83b2789db253... confirmed
2024-05-09 18:40 UTC 500.71 SC 64d234e28e813e79... confirmed
2024-05-06 04:10 UTC 501.13 SC 5aae47cb4c2f06dc... confirmed
2024-05-02 15:40 UTC 500.93 SC f45ee3a83f3cf37d... confirmed
2024-04-28 05:55 UTC 500.45 SC 65e4e1f0f3a9265c... confirmed
2024-04-23 19:25 UTC 500.11 SC 51bd73169e5d8e82... confirmed
Show more...

All-Time Paid Out: 46,309.47 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.