Topic: Blockchain wallet stopped confirming transactions (Read 1694 times)

rebroadcasting the transactions fixed it for me

thanks for help

Glad to help.

Holy shit I figured it out.  With your help, of course.  I was looking at the wrong thing!  The whole time I was looking at the transaction that sent me the btc (which was 200+ confirmations by now) and the two transactions that I sent that comprised a majority of the btc, but I should have been looking at the FIRST transaction that I made.  Because it did the thing where it sent the small amount to the address that I wanted it to, and then the rest of my balance back to me.  I never tried to manually rebrodcast THAT transaction.  You saying the thing about the original transaction made me look at that first one I sent out again and I got the hex data and rebroadcast that one and they just all confirmed!  

So, if this happens to other people, go to the transaction that the bitcoins originated (in my case it wasn't the actual transaction that sent the btc to my wallet, it was the first transaction I tried to make with those bitcoins and rebroadcast THAT joker (I used https://coinb.in/send-raw-transaction.html but I assume there are ways to do it on non-web clients).

The d50fe7...cf2e1e transaction can't confirm because it spends an output from the c5dfec...7d4217 transaction (which isn't yet confirmed).  Therefore, it won't confirm until its parent transaction confirms.

The c5dfec...7d4217 transaction can't confirm because it spends an output from transaction ID dca3a6f7f68636f58bd13136862254d501e3df1a42c540d5b6e4eab9c0f4192c (which isn't yet confirmed). Therefore, it won't confirm until its parent transaction confirms.

So the transaction you are currently waiting on is transaction ID dca3a6f7f68636f58bd13136862254d501e3df1a42c540d5b6e4eab9c0f4192c

It is odd that transaction hasn't confirmed yet since it pays the standard 0.0001 BTC fee, is less than 1 kB, and has no outputs less than 0.00005430 BTC.
I don't fully understand why a miner would have chosen to confirm transaction ID 98e9d99347ca01b5d588afad06c4ccc9dfbbffbe77980e07ade5f67be1a586d1 before confirming transaction ID dca3a6...f4192c.  If I get a chance, I'll look at the transaction selection criteria, but hopefully someone already familiar with that area of the code will stop by with an answer sooner. I suspect it has something to do with the age of the coins being spent.  Priority is determined by the value of the input multiplied by the number of confirmations on the input being spent.  Since the input you are spending is only 0.0408 BTC and only has 262 confirmations right now, it is considered lower priority than most of the other transactions that are currently being accepted into blocks.  Each new block adds a confirmation to the input.  Eventually the input will have enough confirmations to be considered higher priority than other waiting transactions that paid the same fee, and a miner should then include it into a block.

Then each of the children transactions may have to wait equally long for their inputs to build up enough confirmations to have a high enough priority to be confirmed.

If you used a blockchain.info wallet to send the transactions, then it is possible that blockchain.info will stop broadcasting one (or both) of the transactions you've asked about before they confirm.  Blockchain.info has (in the past) typically stopped broadcasting transactions if they haven't confirmed within 3 days.  If that happens, then the bitcoins will return to your wallet and you'll be able to re-attempt the transactions (perhaps with a slightly larger transaction fee this time).
 

well always you will have some delay in such a quantity of transactions.
do not worry, all will be fine

Hey, I just clicked on those IDs and it looks like they eventually went through, 40 hours after you sent them.  That's good to see at least.  I'm curious if your wallet is able to sent/receive like normal now or did whatever this is screw up your wallet for good?

These transactions are now confirmed. The most likely reason for them not to have been confirmed earlier would be if the transaction that sent the bitcoins to you hadn't been confirmed yet.

Recently?  Did it eventually resolve itself? 

Had the same problem.

I'm sorry, I'm still pretty new to bitcoins, I thought if it happened to me maybe it was a common problem.

Yesterday I received this transaction: https://blockchain.info/tx/e9654877aa1b0da873e1cd17a75bda92855b8f43d911ddc9cc16f35931d88829

It seems odd, doesn't have a time or anything although it's been confirmed many times.

I then used those funds to send these:

https://blockchain.info/tx/c5dfec19af6cd31bc9da373b56681a3f3ff8a7c5022b055eaf4fa2dbf07d4217
https://blockchain.info/tx/d50fe7c0af3333d6d608281bed1772c5b94ea305257c6593d06a97598ecf2e1e

You'll see those have no confirmations after over a day.

Thanks for any help you can provide.

Hi,

I don't mean to hijack this thread but I have the exact same problem from blockchain, my transaction ids are below . maybe we can collectively find a solution

https://blockchain.info/tx/d7b7517a0dab7b35758b0ccc89b8fddc3c65733477b54dee5e3971b3c4e937b3
https://blockchain.info/tx/51deee488cfb521047363f09540e35ccce4f2afa7a0b42dd5e088193d2a0d4b4

Both transactions have 0 confirmations for almost 48 hours now. Like the OP, all i want is for the transaction to confirm or the coins to return to the wallet

You've failed to describe the reason that the transactions aren't confirming.

Without additional information it's impossible to know why your transactions aren't being confirmed.

Can you post the transaction ID of the transactions that are not confirming?  Then perhaps we can look them up in the blockchain and give you a better answer.

Yesterday my blockchain web wallet stopped confirming transactions.  I have four now that are just sitting there, unconfirmed, some for 24 hours now.  I attached a miners fee to all of them, and all of them say "Network Propagation 0% (Very Poor)".  I figured maybe they needed to be rebroadcast, so I went to coinb.in and used their "send raw transaction" form, but when I enter the hex data, they all come back as "tx rejected". 

I have no clue what to do.  I'd like these coins either delivered to the addresses that I sent them to yesterday, or back in my wallet to send again (although I fear whatever underlying problem there was may still be there).  Does anyone have any clue as to how I would go about fixing this?  Thanks a bunch.