SiaMining


65eb022a2c3d6b0b65b48e1f518c378b5643e7bbf5759c380d6ea300a200156fe94599300ef0

Statistics

Unpaid Balance
259.26 SC
All-Time Rewards
881,566.61 SC
All-Time Hashes
28,252 PH
Blocks Found
16
Last Share
14:21:57 UTC
(just now)
Hash Rate Valid Shares Stale Shares Invalid Shares Rewards
5 min 601 GH/s 10,747,904 0 (0.0%) 0 (0.0%) 0.98 SC
15 min 494 GH/s 26,476,544 0 (0.0%) 0 (0.0%) 2.43 SC
60 min 536 GH/s 115,081,216 0 (0.0%) 524,288 (0.5%) 10.60 SC
6 hours 580 GH/s 746,848,256 0 (0.0%) 4,194,304 (0.6%) 68.12 SC
24 hours 556 GH/s 2,863,136,768 786,432 (0.0%) 6,291,456 (0.2%) 256.90 SC

Workers (1/1)

Last refreshed: 14:22:01 UTC (just now)

Name Last Share 5 minutes 15 minutes 1 hour 6 hours 24 hours
obeliskjust now
Stratum
601 GH/s
0.0% stale
494 GH/s
0.0% stale
536 GH/s
0.0% stale
580 GH/s
0.6% invalid
556 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
2020-10-23 14:10 UTC 500.61 SC 2433844a793f7a52... confirmed
2020-10-21 14:55 UTC 500.82 SC 4bcb3a969b881045... confirmed
2020-10-19 22:25 UTC 502.72 SC bb32b5956d85d3af... confirmed
2020-10-18 01:10 UTC 501.21 SC 5cfe89547d84c35e... confirmed
2020-10-16 05:10 UTC 501.90 SC 830be16587521c58... confirmed
2020-10-14 09:55 UTC 501.92 SC ac3402b8d8f7f32e... confirmed
2020-10-12 11:25 UTC 500.28 SC c1a463e9c524e4fe... confirmed
2020-10-10 11:55 UTC 501.36 SC 61d8d66c7b174aa4... confirmed
2020-10-08 12:10 UTC 502.13 SC beadceff6be20a98... confirmed
2020-10-06 13:55 UTC 252.02 SC 36250b6b9bfc3472... confirmed
2020-10-01 13:55 UTC 355.71 SC 9e495d193c0abf7a... confirmed
2020-09-26 13:55 UTC 500.18 SC 0b185ef878fbf5e6... confirmed
2020-09-24 16:40 UTC 501.52 SC 6200007e11647f97... confirmed
Show more...

All-Time Paid Out: 881,307.35 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.