Seems like you are not fully synced yet. Let bitmonerod.exe (the daemon) sync for a while until it is at the same block height as moneroblocks.info. You can check this with "diff" or "status" in the daemon. If you are fully synced, refresh your wallet and you should see your transaction.

Unfortinatily bitmonerod refused to sync the last blocks. First bitmonerod crashed and after restarting i got
And i never see the transactions. Status doesn't change with time.

I already tried to delete the entire ./bitmonero folder, just deleting(moving) p2pstate.bin didn't help either. I currently have some problems with arch linux but i fail to see how that would be related to this problem.

Strangely i get
but i am stuck at block 1078355

I did solve the problem just by copying the ./bitmonerod folder from another archlinux installation. Now i do not get any errors.


We can test that my wallet is working further, just donate 1000XMR to 4BKEfR8EYRafz2i3Setbd2ZrTuzffirvLTck6dhpvoCqebAxcSozX6ijMEgbnuFdbe8TiMR5KKsjkci aiqWim7UxKQsf4hC
 
Here is a part of my bitmonero.log:

2016-Jul-04 13:48:30.577933 [P2P8][66.190.86.61:18080 OUT]Sync data returned unknown top block: 1078355 -> 1083807 [5452 blocks (3 days) behind]
SYNCHRONIZATION started
2016-Jul-04 13:48:38.063378 [P2P6][176.31.96.136:18080 OUT]Sync data returned unknown top block: 1078355 -> 1083807 [5452 blocks (3 days) behind]
SYNCHRONIZATION started
2016-Jul-04 13:48:38.123836 [P2P2]ERRORDISTRIBUTION-BUILD/src/cryptonote_core/blockchain.cpp:2757 Error adding block with hash: <f9241b039ccbc6047cda9672168bf036fe971bd800becd1ea61431426ab53914> to blockchain, what = Error adding spent key image to db transaction: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
2016-Jul-04 13:48:38.178664 [P2P4][46.255.20.101:18080 OUT]Sync data returned unknown top block: 1078355 -> 1083807 [5452 blocks (3 days) behind]
SYNCHRONIZATION started
2016-Jul-04 13:48:38.254523 [P2P3][178.254.34.122:18080 OUT]Sync data returned unknown top block: 1078355 -> 1083807 [5452 blocks (3 days) behind]
SYNCHRONIZATION started
2016-Jul-04 13:48:40.512308 [P2P5]DB error attempting to fetch transaction from hashMDB_BAD_TXN: Transaction must abort, has a child, or is invalid
2016-Jul-04 13:48:40.514359 [P2P5]ERRORDISTRIBUTION-BUILD/contrib/epee/include/net/abstract_tcp_server2.inl:355 Exception at [connection<t_protocol_handler>::handle_read], what=DB error attempting to fetch transaction from hashMDB_BAD_TXN: Transaction must abort, has a child, or is invalid
2016-Jul-04 13:48:41.352795 [P2P2]ERRORDISTRIBUTION-BUILD/src/cryptonote_core/blockchain.cpp:2757 Error adding block with hash: <f9241b039ccbc6047cda9672168bf036fe971bd800becd1ea61431426ab53914> to blockchain, what = Error adding spent key image to db transaction: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
2016-Jul-04 13:48:47.921512 [P2P2]DB error attempting to fetch transaction from hashMDB_BAD_TXN: Transaction must abort, has a child, or is invalid
2016-Jul-04 13:48:47.921669 [P2P2]ERRORDISTRIBUTION-BUILD/contrib/epee/include/net/abstract_tcp_server2.inl:355 Exception at [connection<t_protocol_handler>::handle_read], what=DB error attempting to fetch transaction from hashMDB_BAD_TXN: Transaction must abort, has a child, or is invalid
2016-Jul-04 13:48:49.465658 [P2P8][37.59.49.7:28080 OUT]Sync data returned unknown top block: 1078355 -> 1083807 [5452 blocks (3 days) behind]
SYNCHRONIZATION started
2016-Jul-04 13:48:49.531924 [P2P6][188.166.61.194:18080 OUT]Sync data returned unknown top block: 1078355 -> 1083807 [5452 blocks (3 days) behind]
SYNCHRONIZATION started

From IRC:

Hi all,

I've setup a new mining pool at sheepman.mine.bz if some miners care to join me 

Found its first block within one day with under 1Kh/s (guess I'm lucky!) but again more hashing power would be appreciated!

Server is hosted in France with good latency to the UK (where I'm based) and pool fees are currently set to 0.5%.

Cheers all!

can you lower this?
"Minimum Payment Threshold: 0.500 XMR"

Its just to avoid dust, but will happily lower if you have a better suggested value?

Most pools seem to have it set as I do, so I'm inclined to leave it at 0.5XMR for now. Although given your basically all the hashing power I have I'll raise it if you insist and agree to remain loyal to the pool

Moneros pools have a nice rising, its very good.