SiaMining


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

1bb63ec8fd8ba996ebbfbc74e7d2fa783cd0b23b56baec3c6f123b60fe9257a44fc984375525

WARNING: This address has been inactive for 16 days. After 30 days of inactivity, an account may be reset, and any accrued balance forfeited as per the Terms of Service.

Statistics

Unpaid Balance
73.74 SC
All-Time Rewards
649,786.42 SC
All-Time Hashes
543,017 PH
Blocks Found
21
Last Share
22:58:30 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-03-10 20:10 UTC 623.08 SC 5f0ecb7cab1dfbe9... confirmed
2025-03-09 20:10 UTC 618.96 SC 17c04debb3cbe4b9... confirmed
2025-03-08 20:10 UTC 501.63 SC cf259534495994c7... confirmed
2025-03-07 04:40 UTC 546.33 SC 92f03a7ceeb02864... confirmed
2025-03-06 04:40 UTC 655.53 SC 3a5de926c3568448... confirmed
2025-03-05 04:40 UTC 626.48 SC f794940aee784bb8... confirmed
2025-03-04 04:40 UTC 675.51 SC dfdd67f242bb2c45... confirmed
2025-03-03 04:40 UTC 669.60 SC cc434393bb5c5194... confirmed
2025-03-02 04:40 UTC 683.35 SC 1c9c5a54bdd67d2d... confirmed
2025-03-01 04:40 UTC 631.67 SC 34de9a59a98b71bd... confirmed
2025-02-28 04:40 UTC 655.62 SC 8396d9781c75fec7... confirmed
2025-02-27 04:40 UTC 865.38 SC c6f0aff059712ed3... confirmed
2025-02-26 04:40 UTC 1,006.18 SC c41b6bffec4b2d83... confirmed
Show more...

All-Time Paid Out: 649,712.68 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.