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.

bc1a3bef4ec7fb082ebebc85aa3c81c253785a2ffcb6c41670488ea201d81f27cc194c0f492d

Statistics

Unpaid Balance
169.11 SC
All-Time Rewards
101,563.68 SC
All-Time Hashes
45,153 PH
Blocks Found
6
Last Share
17:20:25 UTC
(just now)
Hash Rate Valid Shares Stale Shares Invalid Shares Rewards
5 min 1,261 GH/s 22,544,384 0 (0.0%) 0 (0.0%) 0.53 SC
15 min 870 GH/s 46,661,632 0 (0.0%) 524,288 (1.1%) 1.10 SC
60 min 916 GH/s 196,608,000 0 (0.0%) 1,572,864 (0.8%) 4.65 SC
6 hours 865 GH/s 1,113,587,712 0 (0.0%) 7,340,032 (0.7%) 26.43 SC
24 hours 854 GH/s 4,398,252,032 524,288 (0.0%) 25,427,968 (0.6%) 102.64 SC

Workers (1/1)

Last refreshed: 17:20:30 UTC (just now)

Name Last Share 5 minutes 15 minutes 1 hour 6 hours 24 hours
worker5just now
Stratum
1,261 GH/s
0.0% stale
870 GH/s
1.1% invalid
916 GH/s
0.8% invalid
865 GH/s
0.7% invalid
854 GH/s
0.6% 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-03-26 01:55 UTC 441.81 SC e9ea2e076e4cc0a4... confirmed
2025-03-21 01:55 UTC 400.84 SC 2ee0b4274b21ae72... confirmed
2025-03-16 01:55 UTC 422.03 SC 96eb7b66241857fa... confirmed
2025-03-11 01:55 UTC 376.43 SC 288d68f57f6488ac... confirmed
2025-03-06 01:55 UTC 393.89 SC d40d7e0d6061a704... confirmed
2025-03-01 01:55 UTC 370.22 SC a23c5159ba9b6748... confirmed
Show more...

All-Time Paid Out: 101,394.57 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.