Why is it taking so long to confirm?

[sportsbettingpicks]

The fee is there.. It's been over 5 hours I'm waiting for this to confirm.

https://blockchain.info/tx/ed3339dc53a0732db18b39932349f0bc59371526583481b39435fa7231ee4035

[1714893974]

1714893974

[1714893974]

1714893974

[RodeoX]

Could it be the "stress test" that someone here is launching? Basically they are DDOSing the blockchain today.

[sportsbettingpicks]

I saw someone saying somewhere to push the tx I'd to broadcast it.. How do I do that?

[DannyHamilton]

This transaction: ed3339dc53a0732db18b39932349f0bc59371526583481b39435fa7231ee4035

is not confirming because it spends an output that was received in transaction: a044109ce65973fb0a567e34ab1e4237e0718e5b4b0984e3fff939c20e3dc34d

and that transaction is not confirmed yet.  The transaction you are asking about CAN NOT confirm until the transaction that funds it confirms.

Unfortunately, that earlier transaction only paid a fee of 0.00002260 BTC (10 satoshis per byte), so it may take a while for it to confirm (if ever).

Well written wallet software should not allow you to accidentally spend unconfirmed outputs in your transactions.  This means that you are either using a poorly written wallet (and you should inform the wallet developer that their wallet is a piece of crap that needs to be fixed ASAP), or you made a decision yourself to take on the risks associated with spending unconfirmed outputs (and you shouldn't make such decisions if you don't understand the risks).

[dsattler]

Could it be the "stress test" that someone here is launching? Basically they are DDOSing the blockchain today.

Yes, they're doing it again:

http://blogs.wsj.com/moneybeat/2015/06/30/bitbeat-coinwallet-runs-another-stress-test/?mod=WSJBlog

[ingiltere]

This transaction: ed3339dc53a0732db18b39932349f0bc59371526583481b39435fa7231ee4035

is not confirming because it spends an output that was received in transaction: a044109ce65973fb0a567e34ab1e4237e0718e5b4b0984e3fff939c20e3dc34d

and that transaction is not confirmed yet.  The transaction you are asking about CAN NOT confirm until the transaction that funds it confirms.

Unfortunately, that earlier transaction only paid a fee of 0.00002260 BTC (10 satoshis per byte), so it may take a while for it to confirm (if ever).

Well written wallet software should not allow you to accidentally spend unconfirmed outputs in your transactions.  This means that you are either using a poorly written wallet (and you should inform the wallet developer that their wallet is a piece of crap that needs to be fixed ASAP), or you made a decision yourself to take on the risks associated with spending unconfirmed outputs (and you shouldn't make such decisions if you don't understand the risks).

I'm using Bitcoin Core and I can send unconfirmed unspent outputs. Is Bitcoin Core poorly written wallet?

Ps: If you send bitcoins from yourself to yourself on bitcoin core, then you can spend the zero confirmed unspent output...

[Hexcoin]

This transaction: ed3339dc53a0732db18b39932349f0bc59371526583481b39435fa7231ee4035

is not confirming because it spends an output that was received in transaction: a044109ce65973fb0a567e34ab1e4237e0718e5b4b0984e3fff939c20e3dc34d

and that transaction is not confirmed yet.  The transaction you are asking about CAN NOT confirm until the transaction that funds it confirms.

Unfortunately, that earlier transaction only paid a fee of 0.00002260 BTC (10 satoshis per byte), so it may take a while for it to confirm (if ever).

Well written wallet software should not allow you to accidentally spend unconfirmed outputs in your transactions.  This means that you are either using a poorly written wallet (and you should inform the wallet developer that their wallet is a piece of crap that needs to be fixed ASAP), or you made a decision yourself to take on the risks associated with spending unconfirmed outputs (and you shouldn't make such decisions if you don't understand the risks).

I'm using Bitcoin Core and I can send unconfirmed unspent outputs. Is Bitcoin Core poorly written wallet?

Ps: If you send bitcoins from yourself to yourself on bitcoin core, then you can spend the zero confirmed unspent output...

AFAIK you can only send the unspent outputs if the transaction have the minimum required fees which make the transaction in high priority

[jonnybravo0311]

This transaction: ed3339dc53a0732db18b39932349f0bc59371526583481b39435fa7231ee4035

is not confirming because it spends an output that was received in transaction: a044109ce65973fb0a567e34ab1e4237e0718e5b4b0984e3fff939c20e3dc34d

and that transaction is not confirmed yet.  The transaction you are asking about CAN NOT confirm until the transaction that funds it confirms.

Unfortunately, that earlier transaction only paid a fee of 0.00002260 BTC (10 satoshis per byte), so it may take a while for it to confirm (if ever).

Well written wallet software should not allow you to accidentally spend unconfirmed outputs in your transactions.  This means that you are either using a poorly written wallet (and you should inform the wallet developer that their wallet is a piece of crap that needs to be fixed ASAP), or you made a decision yourself to take on the risks associated with spending unconfirmed outputs (and you shouldn't make such decisions if you don't understand the risks).

I'm using Bitcoin Core and I can send unconfirmed unspent outputs. Is Bitcoin Core poorly written wallet?

Ps: If you send bitcoins from yourself to yourself on bitcoin core, then you can spend the zero confirmed unspent output...

AFAIK you can only send the unspent outputs if the transaction have the minimum required fees which make the transaction in high priority

I wasn't aware that the core software even let you spend the unconfirmed transactions in the first place, unless you've chosen to allow it in the options.  Every time I've tried to send more coins than showed in my available balance, the core software has told me I cannot do it.  Obviously OP overrode that without understanding the consequences of doing so and is now wondering why things aren't playing nicely.

[Blawpaw]

It can take up to 6 hours for you to get your bitcoins. Currently, you need to wait for 30 confirmation to know the transaction is validated. There was some bug on the protocol that left Bitcoin wallets vulnerable to double spending... For now the issue is being addressed and the longer confirmation period is going to be lowered as soon as the issue is solved!

here, take a look:

http://bitcoinist.net/mtgox-deadline-filing-bankruptcy-extended/

[ranochigo]

It can take up to 6 hours for you to get your bitcoins. Currently, you need to wait for 30 confirmation to know the transaction is validated. There was some bug on the protocol that left Bitcoin wallets vulnerable to double spending... For now the issue is being addressed and the longer confirmation period is going to be lowered as soon as the issue is solved!

here, take a look:

http://bitcoinist.net/mtgox-deadline-filing-bankruptcy-extended/

I believe the but would only affect Bitcoin Core ver 0.09.4 and below and SPV clients are unsafe as those version of Bitcoin Core don't know about the BIP66 upgrade and wouldn't reject the invalid block that Core 0.9.5+ versions would reject. SPV clients just trust the miners to be following the correct rules. The link is completely unrelated btw.