SiaMining


4ee6b99ccfdb2adefead0b71aa7891f6a1a2d8ae9e0b00fcf8f781b23ebc24754ea3f669fe59

Statistics

Unpaid Balance
359.48 SC
All-Time Rewards
2,081,320.56 SC
All-Time Hashes
18,351 PH
Blocks Found
13
Last Share
09:16:08 UTC
(just now)
Hash Rate Valid Shares Stale Shares Invalid Shares Rewards
5 min 836 GH/s 14,942,208 0 (0.0%) 0 (0.0%) 12.19 SC
15 min 762 GH/s 40,894,464 0 (0.0%) 0 (0.0%) 33.40 SC
60 min 669 GH/s 143,654,912 0 (0.0%) 262,144 (0.2%) 117.80 SC
6 hours 658 GH/s 847,511,552 0 (0.0%) 262,144 (0.0%) 690.58 SC
24 hours 649 GH/s 3,344,433,152 0 (0.0%) 3,407,872 (0.1%) 2,738.21 SC

Workers (1/1)

Last refreshed: 09:16:14 UTC (just now)

Name Last Share 5 minutes 15 minutes 1 hour 6 hours 24 hours
obelisk2just now
Stratum
836 GH/s
0.0% stale
762 GH/s
0.0% stale
669 GH/s
0.0% stale
658 GH/s
0.0% stale
649 GH/s
0.0% stale

Recent Payouts

Payouts are performed daily with a threshold of 500 SC, or up to every 6 hours when over 1000 SC.

Date/TimeAmountTransaction IDStatus
2019-05-19 06:10 UTC 1,024.01 SC ab6acfe86eb7aa5a... confirmed
2019-05-18 21:10 UTC 1,020.86 SC a81093b86cca574d... confirmed
2019-05-18 12:10 UTC 1,026.95 SC 007db7c92b7b5c15... confirmed
2019-05-18 02:10 UTC 525.23 SC 793aa77d68bc4916... confirmed
2019-05-13 21:55 UTC 105.37 SC 044ebff366fef854... confirmed
2019-04-23 16:10 UTC 1,000.21 SC e41f380cb40d058d... confirmed
2019-04-23 01:55 UTC 1,004.50 SC f3cf5003e4ba7670... confirmed
2019-04-22 11:55 UTC 1,009.77 SC b28f6c0914538418... confirmed
2019-04-21 22:55 UTC 1,016.26 SC 182fd000e483cf42... confirmed
2019-04-21 10:25 UTC 1,018.33 SC 520fedc6f6e0dc53... confirmed
2019-04-20 20:55 UTC 1,003.34 SC ccbf34e8ecb725ee... confirmed
2019-04-20 07:40 UTC 1,002.46 SC df0afe1fc5d4b511... confirmed
2019-04-19 17:10 UTC 1,012.12 SC 1967b62bd87086df... confirmed
Show more...

All-Time Paid Out: 2,080,961.08 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.