I can see these transactions, they have been propagated, even if they are not shown at blockchain.info.
bb170b204b7d7b6c4eff47e7c30414eb287ddab7a36c21583fe05e0a1c8cfd79
-> this is a transaction to Satoshi dice. it looks normal, but it depends on outputs from 514b2cb48fcecc609b72ace23970161541fcafb4f1dbff586265a3f360a4ea5e
514b2cb48fcecc609b72ace23970161541fcafb4f1dbff586265a3f360a4ea5e
-> this is a very big transaction, with 129 outputs, and very small output amounts.
it is an incoming transaction, you received 1340 satoshis there.
this transaction is considered as spam by the bitcoin network, because of the new rules. (see:
https://bitcointalksearch.org/topic/warning-bitcoin-will-soon-block-small-transaction-outputs-196138)
Do you know where it comes from?
27ab2b68c40172cf3be268d485667514ea6f7dc9a13790ed114a0430728c35b3
-> looks normal, but depends on bb170b204b7d7b6c4eff47e7c30414eb287ddab7a36c21583fe05e0a1c8cfd79
so, the problem is caused by bb170b204b7d7b6c4eff47e7c30414eb287ddab7a36c21583fe05e0a1c8cfd79.
this transaction will never go in the blockchain because of the new rules since may 15.
Therefore Electrum servers should block it too. In other words, it is a server bug.
Electrum servers should update to bitcoind 0.8.2, so that this transaction will disappear. (and the other two will disapear too)
I cannot do that now, because my server is currently down, so may I ask other server operators to upgrade their bitcoind?
note: you may just just stop and restart your bitcoind and your electrum server, this too will fix this user's problem,
but it won't prevent it from happening again.
@dermo: sorry for the inconvenience. I hope some server gets upgraded soon.