the dust threshold was set to high.... so it wouldnt show the transaction!
Thanks for coming back and reporting what the issue was.
I probably wouldn't have thought about that. The logs showed everything is fine, so i would have assumed that this is a bug.
I will keep this in mind in case someone else is running into such an issue.
Not really a problem, but it can behave a bit buggy regarding displaying new incoming transactions.
Someone had a problem roughly 2 weeks ago, where he was running 2 instances at the same time and didn't see an incoming transaction. The reason was that you don't see incoming transactions in a second instance until the TX is confirmed.
While this wasn't the case here, running 2 instances still could have caused some other displaying issues. Therefore i asked