SiaMining


e4f5734fd95768b25f25bc28b1c49788d9a069b0920182052442f415e81ff3c469d808a46474

Statistics

Unpaid Balance
376.08 SC
All-Time Rewards
816,788.31 SC
All-Time Hashes
32,414 PH
Blocks Found
11
Last Share
21:28:57 UTC
(just now)
Hash Rate Valid Shares Stale Shares Invalid Shares Rewards
5 min 425 GH/s 7,602,176 0 (0.0%) 0 (0.0%) 0.38 SC
15 min 440 GH/s 23,592,960 0 (0.0%) 0 (0.0%) 1.19 SC
60 min 512 GH/s 109,838,336 0 (0.0%) 1,048,576 (0.9%) 5.60 SC
6 hours 501 GH/s 645,398,528 0 (0.0%) 2,621,440 (0.4%) 32.80 SC
24 hours 521 GH/s 2,683,305,984 0 (0.0%) 6,553,600 (0.2%) 134.64 SC

Workers (1/1)

Last refreshed: 21:29:02 UTC (just now)

Name Last Share 5 minutes 15 minutes 1 hour 6 hours 24 hours
obelisk1just now
Stratum
425 GH/s
0.0% stale
440 GH/s
0.0% stale
512 GH/s
0.9% invalid
501 GH/s
0.0% stale
521 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
2021-05-10 02:10 UTC 500.29 SC 350d665a58fee81c... confirmed
2021-05-07 04:25 UTC 500.70 SC cd265459be03ee1e... confirmed
2021-05-04 12:40 UTC 500.41 SC e271c319f951af1c... confirmed
2021-04-30 21:40 UTC 493.43 SC 515b46756a630e02... confirmed
2021-04-25 21:40 UTC 500.59 SC c5be5e400a4e6d9a... confirmed
2021-04-22 07:55 UTC 501.42 SC 56d5e8aa681b48a7... confirmed
2021-04-19 04:55 UTC 500.28 SC cb6e80006a40175c... confirmed
2021-04-16 04:40 UTC 500.78 SC 534726f0a1e84fdb... confirmed
2021-04-13 01:40 UTC 500.10 SC 8095cdafe56e3407... confirmed
Show more...

All-Time Paid Out: 816,412.23 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.