SiaMining


094ee09bcf3e7d8832699a19ed19fc57ab5b484c1981be2b85db6465910ac9c374d241397f2b

Statistics

Unpaid Balance
206.02 SC
All-Time Rewards
73,208.95 SC
All-Time Hashes
48,132 PH
Blocks Found
2
Last Share
21:17:52 UTC
(just now)
Hash Rate Valid Shares Stale Shares Invalid Shares Rewards
5 min 1,730 GH/s 24,641,536 6,291,456 (20.3%) 0 (0.0%) 0.45 SC
15 min 1,876 GH/s 94,371,840 6,291,456 (6.3%) 0 (0.0%) 1.72 SC
60 min 1,774 GH/s 380,633,088 0 (0.0%) 1,310,720 (0.3%) 6.93 SC
6 hours 1,728 GH/s 2,224,029,696 524,288 (0.0%) 6,029,312 (0.3%) 40.17 SC
24 hours 1,729 GH/s 8,899,002,368 2,621,440 (0.0%) 15,990,784 (0.2%) 158.39 SC

Workers (1/1)

Last refreshed: 21:17:58 UTC (just now)

Name Last Share 5 minutes 15 minutes 1 hour 6 hours 24 hours
SC1just now
Stratum
1,730 GH/s
20.3% stale
1,876 GH/s
6.3% stale
1,774 GH/s
0.0% stale
1,728 GH/s
0.0% stale
1,729 GH/s
0.0% stale

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
2024-09-18 14:55 UTC 500.42 SC c86c9f77ea5a27d9... confirmed
2024-09-15 18:40 UTC 500.11 SC e955b2df4561a644... confirmed
2024-09-12 18:25 UTC 500.65 SC 831d3b180567cc37... confirmed
2024-09-08 23:40 UTC 100.47 SC 5fd181dbef7616f9... confirmed
2024-08-31 23:55 UTC 182.67 SC 4806e1d15fd52962... confirmed
2024-08-26 23:55 UTC 500.04 SC 4a420e1a2821af01... confirmed
2024-08-23 20:55 UTC 501.65 SC 209759e91641af21... confirmed
2024-08-21 02:10 UTC 501.15 SC 29b0a268d4878b51... confirmed
Show more...

All-Time Paid Out: 73,002.93 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.