84.27Bitcoins, 24 hours unconfirmed! need help.

[xuanxuan3317]

I sent 84.27B to the address 193vBkTSaZ2wCm8vTvFqjX7hGsas5kggtR, after 24 hours it still shows that unconfirmed transaction. Is there any one can help me to deal with this situation？ 
 transaction record is ab497952714bcc8970aa186b9557880473b6f449e53dc8107bb3d19bcca0a4d6. Please help me！

[blueadept]

One of the inputs is an output of an unconfirmed transaction, which is preventing the transaction from getting confirmed.  The unconfirmed transaction is from SatoshiDice, so it may take a while.

[elor70]

just wait... if tis more than week you should start worring but you ahev nothing to do about it.

[Mike Hearn]

For now you just have to wait until the SD transaction is mined.

There is a change pending review that would help in situations like this:

https://github.com/bitcoin/bitcoin/pull/2814

It would mean you could attach a higher fee to your second transaction and it would encourage mining of the first. But the code isn't merged yet.

[TierNolan]

So, the client will spend outputs, even if they aren't in any block?

[cp1]

So, the client will spend outputs, even if they aren't in any block?

I think they're saying that's the problem.  Part of the OP's transaction has an unconfirmed output as an input.  So he's waiting on that output to be confirmed so that his transaction can be valid to be mined.  The unconfirmed output isn't being confirmed because it's low fee and low priority.  Mike's code change would be for the OP's fee to be used to bump up the priority of the unconfirmed output he's waiting on.

[Peter Todd]

For now you just have to wait until the SD transaction is mined.

There is a change pending review that would help in situations like this:

https://github.com/bitcoin/bitcoin/pull/2814

It would mean you could attach a higher fee to your second transaction and it would encourage mining of the first. But the code isn't merged yet.

Luke-Jr's pull-req is the completed one: https://github.com/bitcoin/bitcoin/pull/1647 My code is just taking his idea and applying it in a way that is more general and reliable. (Luke's patch is good, it's just you can extend the idea even further with P2P protocol changes so nodes can know how to retrieve parent transactions if required)

Eligius and another pool uses Luke's patch already, so re-spending your stuck transaction with a fee will help. Unfortunately I don't think any Bitcoin wallets have an easy way to do this; it'd be really good if someone writes that code. The user should be able to click on a payment, either to you or from you to someone else, and say "Increase fee" and have the wallet software take the correct steps.

[TierNolan]

Part of the OP's transaction has an unconfirmed output as an input.

An easier fix would be for the client to not use unconfirmed outputs as inputs (or at least display a warning).

[Peter Todd]

Part of the OP's transaction has an unconfirmed output as an input.

An easier fix would be for the client to not use unconfirmed outputs as inputs (or at least display a warning).

Bitcoin-QT doesn't do that unless the output is one of your own.

The OP is using a different wallet - you can tell because the keys aren't compressed.