SiaMining


IMPORTANT: This mining pool is closed as of May 1, 2025. Final payouts have been issued. Please migrate your miners to another pool.

dd559f67784d475e086aec2f80fd464cdcd5122522b8054004b54821ab9c5ea47d441ea92344

Statistics

Unpaid Balance
0.00 SC
All-Time Rewards
7,292,725.41 SC
All-Time Hashes
3,696,886 PH
Blocks Found
258
Last Share
22:24:52 UTC
(2 weeks ago)

Not currently mining.

Workers

No workers defined.

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-04-27 09:25 UTC 431.31 SC 0e058b4f64486f69... confirmed
2025-04-22 09:25 UTC 819.18 SC cbe510e0c89883d8... confirmed
2025-04-21 09:25 UTC 832.43 SC 378b1c87676a822d... confirmed
2025-04-20 09:25 UTC 788.43 SC 438434502b2984df... confirmed
2025-04-19 09:25 UTC 778.05 SC 0fad59532d95db27... confirmed
2025-04-18 09:25 UTC 747.19 SC afd7054e171923de... confirmed
2025-04-17 09:25 UTC 692.19 SC fed7620d88bd56ca... confirmed
2025-04-16 09:25 UTC 691.67 SC 35b73a1b6a91ced8... confirmed
2025-04-15 09:25 UTC 718.73 SC e7081ea2c83d19ef... confirmed
2025-04-14 09:25 UTC 710.04 SC 7d682fbc84d029bd... confirmed
2025-04-13 09:25 UTC 827.83 SC 973e42f6e2d6aa3a... confirmed
2025-04-12 09:25 UTC 946.31 SC b1f64002449ee97b... confirmed
2025-04-11 09:25 UTC 949.95 SC 534045e439923960... confirmed
2025-04-10 09:25 UTC 872.30 SC 118fedc413cd5b17... confirmed
2025-04-09 09:25 UTC 848.83 SC d9052e9d2cc6d381... confirmed
Show more...

All-Time Paid Out: 7,292,725.41 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.