Is the blockchain messed up or did I get screwed out of bitcoin?

[D35TR0Y3R]

I have recently noticed that my online wallet at blockchain.info has been REALLY fucked up. I've been getting weird node propogation rates, usually around 60% before it confirms. Just now, I've had them fail at 40%, which doesnt make sense to me at all. Also, if I let it use an automatic tx fee, it's 10-20x higher than the normal 0.5mbtc. Here's an example of 0.12 I just got screwed out of https://blockchain.info/tx/6030f180a49391f052ad23dc21fa617c4eda4cffec0f88b2287f8a463b9f774f . And the weirdest part I think is that I've recieved my bitcoin from numerous different sources. So how can I have that many invalid bitcoin? Also, if my transaction calls on many different inputs, and just one of those were invalid, such as if it came from when the blockchain forked, why would it say that the whole transaction worth of bitcoin was lost?

tl;dr: A bunch of stuff that doesnt make sense to a noob.

[1CHBhqws]

... my transaction calls on many different inputs...

This is your basic problem.
If you compare the following two transactions:
https://blockchain.info/tx/6030f180a49391f052ad23dc21fa617c4eda4cffec0f88b2287f8a463b9f774f
https://blockchain.info/tx/f3a513986ac4c06d57331e79e641da0d0e966c5c0ac305267285fbf679f7b8e4

you'll see that the first spends lots of inputs, so the total space required in a block (and thus the blockchain) is 3680 bytes, because it needs to provide lots of different signatures to lots of different inputs.

The second, however, sends the same BTC value to the same address, but only spends a single input. As such it requires only 259 bytes of space in the block.

A miner will much prefer the second one to the first... indeed, it could fit 14 different transactions like the second one in the same amount of space in the block as the first, making it over an order of magnitude more profitable for the miner.


Both are valid, and should EVENTUALLY be included in a block... it's just that the first has a lower fee than much of the network would expect for a transaction taking up so much space, so will likely take a long time to confirm.

[D35TR0Y3R]

... my transaction calls on many different inputs...

This is your basic problem.
If you compare the following two transactions:
https://blockchain.info/tx/6030f180a49391f052ad23dc21fa617c4eda4cffec0f88b2287f8a463b9f774f
https://blockchain.info/tx/f3a513986ac4c06d57331e79e641da0d0e966c5c0ac305267285fbf679f7b8e4

you'll see that the first spends lots of inputs, so the total space required in a block (and thus the blockchain) is 3680 bytes, because it needs to provide lots of different signatures to lots of different inputs.

The second, however, sends the same BTC value to the same address, but only spends a single input. As such it requires only 259 bytes of space in the block.

A miner will much prefer the second one to the first... indeed, it could fit 14 different transactions like the second one in the same amount of space in the block as the first, making it over an order of magnitude more profitable for the miner.


Both are valid, and should EVENTUALLY be included in a block... it's just that the first has a lower fee than much of the network would expect for a transaction taking up so much space, so will likely take a long time to confirm.

Well shit. I sent double of anything that hadnt confirmed in a real long time. Hope I can get refunds :/ Is there some way that I can turn it into one input?

[D35TR0Y3R]

Is there some way that I can cancel those transactions? Seeing as they only have gone through 17 nodes, it's not going to confirm for a very long time.

[grue]

Is there some way that I can cancel those transactions? Seeing as they only have gone through 17 nodes, it's not going to confirm for a very long time.

no, although it will eventually be dropped from each peer's memory pool.

[D35TR0Y3R]

Is there some way that I can cancel those transactions? Seeing as they only have gone through 17 nodes, it's not going to confirm for a very long time.

no, although it will eventually be dropped from each peer's memory pool.

So basically my stupidity just lost me 0.2 btc?

[1CHBhqws]

I see that both transactions are now well-confirmed. So if you'd not meant to send both, any return of overpayment would be up to you to sort out with the recipient.

[TierNolan]

So basically my stupidity just lost me 0.2 btc?

If the transaction never clears, then you should be able to re-spend the coins somewhere else. 

What you could try is to copy your wallet.dat to an install.  I am not sure if the wallet records that a transaction has been made with that coin.  If not, since the transaction is not in the block chain, the new client will not know anything about it, but will have all the keys to spend the coin.