SiaMining


50400e14cd2e0a0c01f75de37c4d65b5331867ceb80cde99474da7967423f891e41306b3d67e

Statistics

Unpaid Balance
406.15 SC
All-Time Rewards
4,654,126.43 SC
All-Time Hashes
633,218 PH
Blocks Found
35
Last Share
08:36:28 UTC
(2 hours ago)
Hash Rate Valid Shares Stale Shares Invalid Shares Rewards
5 min 0.0 MH/s 0 0 (0.0%) 0 (0.0%) 0.00 SC
15 min 0.0 MH/s 0 0 (0.0%) 0 (0.0%) 0.00 SC
60 min 0.0 MH/s 0 0 (0.0%) 0 (0.0%) 0.00 SC
6 hours 25.0 GH/s 32,243,712 0 (0.0%) 0 (0.0%) 35.82 SC
24 hours 18.2 GH/s 93,847,552 0 (0.0%) 1,310,720 (1.4%) 104.94 SC

Workers (0/5)

Last refreshed: 10:29:26 UTC (just now)

Name Last Share 5 minutes 15 minutes 1 hour 6 hours 24 hours
L0010003296 hours ago
Stratum
2,443 MH/s
0.0% stale
2,240 MH/s
0.0% stale
L0020004415 hours ago
Stratum
3,258 MH/s
0.0% stale
4,123 MH/s
0.0% stale
L0030001263 hours ago
Stratum
4,479 MH/s
4.3% invalid
L004002904 hours ago
Stratum
5,498 MH/s
0.0% stale
3,869 MH/s
1.3% invalid
L0050003742 hours ago
Stratum
8,145 MH/s
0.0% stale
3,512 MH/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-04-19 04:10 UTC 502.67 SC 5f0da36c28b73e16... confirmed
2019-04-15 19:10 UTC 564.38 SC 1932ca2cd49d7161... confirmed
2019-04-11 19:55 UTC 505.32 SC 3b27848c3268fdf0... confirmed
2019-04-07 18:25 UTC 501.22 SC b01749d5ee075620... confirmed
2019-04-05 09:10 UTC 502.82 SC 7db448d5400b59da... confirmed
2019-04-03 04:25 UTC 504.06 SC c018aee5cd2ecc5f... confirmed
2019-03-30 13:40 UTC 500.63 SC bf706afb9e78753c... confirmed
2019-03-27 20:55 UTC 500.51 SC 3987a93f2cac66b0... confirmed
2019-03-26 08:40 UTC 504.43 SC 8c1be5a389b012db... confirmed
2019-03-23 14:25 UTC 502.33 SC b0272bf9eba0fc93... confirmed
Show more...

All-Time Paid Out: 4,653,720.28 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.