IMPORTANT: This mining pool is closed as of May 1, 2025. Final payouts have been issued. Please migrate your miners to another pool.
dd24c972217171d5396503377b5ce38d0c647bc3d86553ab3ba57d81504a23ab9f1d6e240ed0
Statistics
- Unpaid Balance
- 0.00 SC
- All-Time Rewards
- 151,960.25 SC
- All-Time Hashes
- 110,218 PH
- Blocks Found
- 6
- Last Share
- 11:21:33 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/Time | Amount | Transaction ID | Status |
|---|---|---|---|
| 2025-05-01 12:10 UTC | 240.26 SC | 019d0a4cc2fcf3d125fd2ad9fa8a437aeb9293bd992dcdbde3f61a423e2083d3... | confirmed |
| 2025-04-27 08:55 UTC | 500.87 SC | 54c750df59814c97e13adc74e6d4675ab905bf961a863ee505902edd70a525db... | confirmed |
| 2025-04-24 23:55 UTC | 501.92 SC | 90ecf6e4d46f759006af89794a04767c0030cb1e26d78e4408138c6a0b3b6e5d... | confirmed |
| 2025-04-22 14:25 UTC | 501.79 SC | d87c4566664b4883d3d550f269f4927afe7ecd6846c88d461e75c672e212742d... | confirmed |
| 2025-04-20 09:10 UTC | 500.77 SC | 1f1bcd6e6028c189c6e98930f423d6847879d10af2ffa7d1364131eefa1e4d2e... | confirmed |
| 2025-04-17 16:25 UTC | 501.11 SC | 27edb8d4ae3e465f5440b1c6407c705fb42d8f47a106915b54ae1a493c3dcd8a... | confirmed |
| 2025-04-15 01:10 UTC | 500.54 SC | 72cfb10fa6c3f5df0acc16cc5e6952109e501888fa341c40a6db3286bf70386a... | confirmed |
| 2025-04-10 17:40 UTC | 502.20 SC | 2b02fbbaa83d2488c5abc981f21df5d39625af074219c8f60cdaaa2178ed9b58... | confirmed |
| Show more... | |||
All-Time Paid Out: 151,960.25 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.