Sent transaction over 8 hours ago. Still hasn't confirmed. Over 6k! Help!!

[lenkug]

https://blockchain.info/tx/c7594d44b14fb8ed1e36882a37b022a9fd8e9d95c00e6964a8fdf50e574dac99

I think what happened is one of the inputs was too small too send and it made the txn non-standard.

Is there anything I can do except hope that a miner running old software picks it up??

[1715322359]

1715322359

[1715322359]

1715322359

[1715322359]

1715322359

[1715322359]

1715322359

[MineForeman.com]

This is your problem;-

https://blockchain.info/address/1BFGYHR9tVHFGerhdMRKyZXJyvC5ELHtDh

It is a good example of why you should not re-use addresses.  

Having said that, you just need to give it some time now, it is valid and it will eventually confirm.  Paying the minimum fee would have helped though.

Neil

[Ejaculation]

All I know, when it shows: Estimated Confirmation Time   Unknown (Low Priority)

That means bad news for you. I'd estimate around 3 weeks before it gets confirmed, you could be waiting even longer.

[lenkug]

This is your problem;-

https://blockchain.info/address/1BFGYHR9tVHFGerhdMRKyZXJyvC5ELHtDh

It is a good example of why you should not re-use addresses.  

Having said that, you just need to give it some time now, it is valid and it will eventually confirm.  Paying the minimum fee would have helped though.

Neil

Will a miner running an updated version of bitcoin be able to propagate the txn??

[DannyHamilton]

Dust output, and insufficient fee.

All you can do now is wait.

Any well written wallet software should have protected you from creating such a transaction.

Would you mind sharing with us what wallet you used so that we all will know not to use that software?

[Ejaculation]

Dust output, and insufficient fee.

All you can do now is wait.

Any well written wallet software should have protected you from creating such a transaction.

Would you mind sharing with us what wallet you used so that we all will know not to use that software?

I've had this happen multiple times with blockchain. Blockchain seems to be the wallet that causes this the most.

[lenkug]

Dust output, and insufficient fee.

All you can do now is wait.

Any well written wallet software should have protected you from creating such a transaction.

Would you mind sharing with us what wallet you used so that we all will know not to use that software?

I've had this happen multiple times with blockchain. Blockchain seems to be the wallet that causes this the most.

Bingo.
Will rebroadcasting the txn work? With the dust added to miner fee?

[DannyHamilton]

Dust output, and insufficient fee.

All you can do now is wait.

Any well written wallet software should have protected you from creating such a transaction.

Would you mind sharing with us what wallet you used so that we all will know not to use that software?

I've had this happen multiple times with blockchain. Blockchain seems to be the wallet that causes this the most.

Is it a bug in their Android client, their iOS client, their desktop client, their browser extension, or their javascript website?

[DannyHamilton]

Dust output, and insufficient fee.

All you can do now is wait.

Any well written wallet software should have protected you from creating such a transaction.

Would you mind sharing with us what wallet you used so that we all will know not to use that software?

I've had this happen multiple times with blockchain. Blockchain seems to be the wallet that causes this the most.

Bingo.
Will rebroadcasting the txn work? With the dust added to miner fee?

You might be able to re-broadcast from some other wallet.  At the moment, blockchain.info will not let you rebroadcast from their wallet since they already see a transaction using those inputs.  If you wait a few days eventually blockchain.info will forget about the transaction if it doesn't confirm and the balance will show up in your wallet again.  At that time you can re-send the transaction either using custom transactions and including the extra as a miner fee, or including the extra in the amount sent.

[lenkug]

Is it a bug in their Android client, their iOS client, their desktop client, their browser extension, or their javascript website?

I used the website wallet.

[justbtcme]

Ouch! I hope you get those coins confirm soon!

[zvs]

Fee is 0.0001, transaction is over 1kb, should be 0.0002

[amaclin]

Fee is 0.0001, transaction is over 1kb, should be 0.0002

No. The problem is "dust output" of  0.00000094 BTC

[yakuza699]

What you can do is now is:
1.Try to build a raw transaction spending same inputs as the tx that you stated and push it directly to eligius pool.
2.Download Peter Todd's replace by fee tools and use the bump fee feature.
Links:
1.http://eligius.st/~wizkid057/newstats/pushtxn.php
2.https://github.com/petertodd/replace-by-fee-tools

[amaclin]

1.Try to build a raw transaction spending same inputs as the tx that you stated and push it directly to eligius pool.

Wouldn't work. Eligius already contains this transaction and will reject any double-spending.
Eligius will not mine it because it runs 0.8.x bitcoin core and requires fee 0.0001 per kb

OP should wait. May be a day or two. Either some miner will include this tx into a block or it will be possible to doublespend it later

Damn!
It is very bad side of current bitcoin network, that non-standard 0.00000094 BTC output can stuck 12 BTC ($6000+) transfer.

[bitsta]

https://blockchain.info/tx/c7594d44b14fb8ed1e36882a37b022a9fd8e9d95c00e6964a8fdf50e574dac99

I think what happened is one of the inputs was too small too send and it made the txn non-standard.

Is there anything I can do except hope that a miner running old software picks it up??

you used a fee under the min fee.
but checking your out and input scripts shows validity.

so you just have to wait (very long) now as this tx is low priority. next time just use rec. min fee
and it would ve already been confirmed.
another option: you could try double-spending it with a recommended fee.

as for your coins. they are "safe".

cheers
bitsta

[amaclin]

you used a fee under the min fee.

NO! Bitcoin 0.9.x requires 0.00001 btc per kb!

[Dare]

The outputs used in the stuck transaction have now been successfully double-spent with 162 confirmations (so far): https://blockchain.info/tx/a9741842f60ec71127b5c04dd11b2f0616665687722a3f80a1604fc5f52a996b

The original transaction no longer has a chance of confirming, so it should be dropped from the network eventually.