Quote from: gunzeon on October 16, 2014, 09:16:56 PM

Quote from: robinson5 on October 16, 2014, 08:42:32 PM

... save space ..

Any thoughts would be greatly appreciated!

I suggest that you try re-opening the senders anoncoin-qt and seeing that it joins up to the network properly.
ie: move the mouse over the bottom right icons and tool tips will show the number of connections, or, type getpeerinfo in the debug window and you should get a list of all the peers you are connected to

I understand that it - anoncoin-qt - should re-broadcast the transaction if it is not yet done ...

This could explain why your transaction never got sent, with all the intermittent block solving maybe when you sent the transaction was at a time when your client could not find any newer nodes to talk to ... from my experience i've seen the connect count vary greatly with these difficulty fluctuations.

[EDIT]
for instance, i'm connected to 67 nodes atm ( upped MAX_OUTBOUND_CONNECTIONS ), i2p, tor, clearnet
also, stick this in your anoncoin.conf:
addnode=anoncoinmpkoerba.onion

[EDIT2]
but if ur just clearnet, be sure that you have:
noirc=0
discover=1
and also, run the latest client and check your debug.log for version mismatches

The sender has quit and restarted his anoncoin-qt client multiple times over the last week. He also has waited each time for the wallet to sync completely and kept the client open for a while after. He also has made sure he is connected to peers (hence why it is syncing). Just to clarify again, one of the transactions took a few days and the other transaction has yet to confirm and it has been about a week.

Thanks for everyone's help I'm just wondering why this has happened.