SiaMining


IMPORTANT: This mining pool will be shut down on May 1, 2025 (in 66 days). Please migrate your miners to another pool by that date.

cf032747fd6b461d676709ca9cb3b833ca4ce283a76c1ea116c985032ef187300a0088223c2b

Statistics

Unpaid Balance
248.77 SC
All-Time Rewards
1,713,332.97 SC
All-Time Hashes
119,581 PH
Blocks Found
23
Last Share
14:23:35 UTC
(just now)
Hash Rate Valid Shares Stale Shares Invalid Shares Rewards
5 min 792 GH/s 14,155,776 0 (0.0%) 0 (0.0%) 0.25 SC
15 min 704 GH/s 37,748,736 0 (0.0%) 524,288 (1.4%) 0.69 SC
60 min 680 GH/s 146,014,208 0 (0.0%) 1,048,576 (0.7%) 2.66 SC
6 hours 672 GH/s 864,550,912 0 (0.0%) 6,815,744 (0.8%) 15.24 SC
24 hours 672 GH/s 3,457,941,504 262,144 (0.0%) 33,030,144 (0.9%) 59.46 SC

Workers (1/1)

Last refreshed: 14:23:39 UTC (just now)

Name Last Share 5 minutes 15 minutes 1 hour 6 hours 24 hours
Obelisk02just now
Stratum
792 GH/s
0.0% stale
704 GH/s
1.4% invalid
680 GH/s
0.7% invalid
672 GH/s
0.8% invalid
672 GH/s
0.9% invalid

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
2025-02-19 11:25 UTC 271.81 SC 442330829b4a2769... confirmed
2025-02-14 11:25 UTC 270.69 SC d4c3fd09e92e1535... confirmed
2025-02-09 11:25 UTC 301.16 SC 9ed02e016c157c91... confirmed
2025-02-04 11:25 UTC 100.45 SC 69703daeae43c6fa... confirmed
2025-01-29 19:25 UTC 304.87 SC db271dda582f746c... confirmed
2025-01-24 19:25 UTC 277.52 SC 6a7dccf420f88e5e... confirmed
Show more...

All-Time Paid Out: 1,713,084.19 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.