Quote from: Overspeed on June 09, 2014, 12:39:09 PM

Strange that each block I found got the full 90 confirmations before they orphaned.

The thing is: when you are on a bad fork, this requires at least 2 nodes (e.g. your wallet and at least 1 other wallet). So based on your description, what I think that happened is that you and another node ended up being on a bad fork together, and that other node was confirming the blocks (because in the bad fork, those blocks would be considered real.. until you got back in sync with the correct fork). I don't have enough information to go by to confirm that this is what happened, but this is the only explanation for the situation you are describing.

By the way, what you can also do is to check debug.log. This is a logfile which is located in the same directory as your saturncoin.conf. This log contains basically all information, like blocks found (and orphaned). So you will likely be able to get the transaction IDs from there. Then using those transaction IDs you can check whether they exist in the block explorer.

Quote from: Overspeed on June 09, 2014, 12:39:09 PM

As for pools, I have 3.5Mh/s and used to mine on Dedicated Pool. They crashed and or had too many problems so I stopped pool mining. That and they shut down the SAT pool after the wallet issues with 0 coins.

Correct, Dedicatedpool is no longer running as they were having some issues on their end and they did not have the time to fix them, since they were too busy with some other projects (DRK in particular) at the time. However, there are other pools you can use. What you can also do is to primarily mine to a pool, but also have another pool (and/or mining to your local wallet) as a backup (failover). This is something you can very easily setup in cgminer (and similar applications). By doing so, you would primarily mine to the pool, and if that pool goes down, it switches to the failover (which could be your local wallet).