0/Unconfirmed

[420popping]

I tried sending BTC, but it's been at 0/unconfirmed since 9AM. It's now 12PM. I included a tax fee of 0.00000591 BTC. Is this normal? Is there any way to speeding this up?

I'm using bitcoin core

[madonnino]

I tried sending BTC, but it's been at 0/unconfirmed since 9AM. It's now 12PM. I included a tax fee of 0.00000591 BTC. Is this normal? Is there any way to speeding this up?

I'm using bitcoin core

0.00000591 BTC is a low priority fee, minimun to get high priority is 0.0001 btc, just wait, it will be confirmed sooner or later

[Muhammed Zakir]

Just wait or create another transaction with higher fees and broadcast it.

I tried sending BTC, but it's been at 0/unconfirmed since 9AM. It's now 12PM. I included a tax fee of 0.00000591 BTC. Is this normal? Is there any way to speeding this up?

I'm using bitcoin core

0.00000591 BTC is a low priority fee, minimun to get high priority is 0.0001 btc, just wait, it will be confirmed sooner or later

Its 0.0001BTC/kb.

[420popping]

Just wait or create another transaction with higher fees and broadcast it.

I tried sending BTC, but it's been at 0/unconfirmed since 9AM. It's now 12PM. I included a tax fee of 0.00000591 BTC. Is this normal? Is there any way to speeding this up?

I'm using bitcoin core

0.00000591 BTC is a low priority fee, minimun to get high priority is 0.0001 btc, just wait, it will be confirmed sooner or later

Its 0.0001BTC/kb.

How would I do that?

[shorena]

Just wait or create another transaction with higher fees and broadcast it.

I tried sending BTC, but it's been at 0/unconfirmed since 9AM. It's now 12PM. I included a tax fee of 0.00000591 BTC. Is this normal? Is there any way to speeding this up?

I'm using bitcoin core

0.00000591 BTC is a low priority fee, minimun to get high priority is 0.0001 btc, just wait, it will be confirmed sooner or later

Its 0.0001BTC/kb.

How would I do that?

Bitcoin core determines it for you as it figures out the size (in bytes) of the TX. Whether this is normal depends on the things you did not share yet. Whoever receives the bitcoins could try "child pays for parent" to speed things up, but there is no guarantee that it works and its pretty advanced currently.

#1 Are you willing to share the transaction id? If so it would be easier for us to help you. If not that is fine as well, we just have to do more guessing.
#2 Regardless of #1: on what setting did you put the slider that goes from fast (1 block) to normal (25 blocks) or did you set a custom fee?
#3 Regardless of #1 or #2 did you extensivly use faucets in the past? This might result in many tiny (in BTC) inputs that make your TX very large.

[420popping]

Just wait or create another transaction with higher fees and broadcast it.

I tried sending BTC, but it's been at 0/unconfirmed since 9AM. It's now 12PM. I included a tax fee of 0.00000591 BTC. Is this normal? Is there any way to speeding this up?

I'm using bitcoin core

0.00000591 BTC is a low priority fee, minimun to get high priority is 0.0001 btc, just wait, it will be confirmed sooner or later

Its 0.0001BTC/kb.

How would I do that?

Bitcoin core determines it for you as it figures out the size (in bytes) of the TX. Whether this is normal depends on the things you did not share yet. Whoever receives the bitcoins could try "child pays for parent" to speed things up, but there is no guarantee that it works and its pretty advanced currently.

#1 Are you willing to share the transaction id? If so it would be easier for us to help you. If not that is fine as well, we just have to do more guessing.
#2 Regardless of #1: on what setting did you put the slider that goes from fast (1 block) to normal (25 blocks) or did you set a custom fee?
#3 Regardless of #1 or #2 did you extensivly use faucets in the past? This might result in many tiny (in BTC) inputs that make your TX very large.

I have a total of 6 send/receive in my history. In the slider when I went to send, I checked both recommended and send with 0 fee if possible.

[shorena]

Just wait or create another transaction with higher fees and broadcast it.

I tried sending BTC, but it's been at 0/unconfirmed since 9AM. It's now 12PM. I included a tax fee of 0.00000591 BTC. Is this normal? Is there any way to speeding this up?

I'm using bitcoin core

0.00000591 BTC is a low priority fee, minimun to get high priority is 0.0001 btc, just wait, it will be confirmed sooner or later

Its 0.0001BTC/kb.

How would I do that?

Bitcoin core determines it for you as it figures out the size (in bytes) of the TX. Whether this is normal depends on the things you did not share yet. Whoever receives the bitcoins could try "child pays for parent" to speed things up, but there is no guarantee that it works and its pretty advanced currently.

#1 Are you willing to share the transaction id? If so it would be easier for us to help you. If not that is fine as well, we just have to do more guessing.
#2 Regardless of #1: on what setting did you put the slider that goes from fast (1 block) to normal (25 blocks) or did you set a custom fee?
#3 Regardless of #1 or #2 did you extensivly use faucets in the past? This might result in many tiny (in BTC) inputs that make your TX very large.

I have a total of 6 send/receive in my history. In the slider when I went to send, I checked both recommended and send with 0 fee if possible.

Recommonded on which setting? Is the slider to the left or the right or more to the middle?

If I currently set it to the most left and slowest, "normal", 25 blocks setting the recommended fee is 0.00005242 BTC/kb. Assuming by your "total of 6" statement I would guess that your tx is ~250 byte which would make a low fee 1310 satoshi according to my client.

If I currently set it to the most right and fastest, "fast", 1 block setting the recommended fee is 0.00044344 BTC/kb. Assuming the same size a high fee would be 11086 satoshi.

Your fee is significantly below my lowest estimated fee which either means that your client did not have enough data to properly judge what a good fee is or the network changed to quickly for it to adapt.

In all cases, waiting while your client is open will get your TX confirmed eventually.

[420popping]

Just wait or create another transaction with higher fees and broadcast it.

I tried sending BTC, but it's been at 0/unconfirmed since 9AM. It's now 12PM. I included a tax fee of 0.00000591 BTC. Is this normal? Is there any way to speeding this up?

I'm using bitcoin core

0.00000591 BTC is a low priority fee, minimun to get high priority is 0.0001 btc, just wait, it will be confirmed sooner or later

Its 0.0001BTC/kb.

How would I do that?

Bitcoin core determines it for you as it figures out the size (in bytes) of the TX. Whether this is normal depends on the things you did not share yet. Whoever receives the bitcoins could try "child pays for parent" to speed things up, but there is no guarantee that it works and its pretty advanced currently.

#1 Are you willing to share the transaction id? If so it would be easier for us to help you. If not that is fine as well, we just have to do more guessing.
#2 Regardless of #1: on what setting did you put the slider that goes from fast (1 block) to normal (25 blocks) or did you set a custom fee?
#3 Regardless of #1 or #2 did you extensivly use faucets in the past? This might result in many tiny (in BTC) inputs that make your TX very large.

I have a total of 6 send/receive in my history. In the slider when I went to send, I checked both recommended and send with 0 fee if possible.

Recommonded on which setting? Is the slider to the left or the right or more to the middle?

If I currently set it to the most left and slowest, "normal", 25 blocks setting the recommended fee is 0.00005242 BTC/kb. Assuming by your "total of 6" statement I would guess that your tx is ~250 byte which would make a low fee 1310 satoshi according to my client.

If I currently set it to the most right and fastet, "fast", 1 block setting the recommended fee is 0.00044344 BTC/kb. Assuming the same size a high fee would be 11086 satoshi.

Your fee is significantly below my lowest estimated fee which either means that your client did not have enough data to properly judge what a good fee is or the network changed to quickly for it to adapt.

In all cases, waiting while your client is open will get your TX confirmed.

Yeah, the slider was all the way to the left. The sending amount was .16.
So pretty much just keep my bitcoin core open? Thanks for your help btw.

I checked blockchain.info and my transaction is there. It's just taking a century to confirm.

[shorena]

-snip-
Yeah, the slider was all the way to the left. The sending amount was .16.
So pretty much just keep my bitcoin core open? Thanks for your help btw.

Yes, keeping it open will make sure that your transaction does not get forgotten by the network as the client will rebroadcast it from time to time. For the future it also helps to keep the client open for a while before you send a TX (more than just syncing) this allows it to collect enough other TX to make a good judgement on how high the fee should be.

[420popping]

-snip-
Yeah, the slider was all the way to the left. The sending amount was .16.
So pretty much just keep my bitcoin core open? Thanks for your help btw.

Yes, keeping it open will make sure that your transaction does not get forgotten by the network as the client will rebroadcast it from time to time. For the future it also helps to keep the client open for a while before you send a TX (more than just syncing) this allows it to collect enough other TX to make a good judgement on how high the fee should be.

Hope this doesn't take forever, it's still unconfirmed

edit: jesus it finally confirmed, again, thanks for the info man!

[philipma1957]

-snip-
Yeah, the slider was all the way to the left. The sending amount was .16.
So pretty much just keep my bitcoin core open? Thanks for your help btw.

Yes, keeping it open will make sure that your transaction does not get forgotten by the network as the client will rebroadcast it from time to time. For the future it also helps to keep the client open for a while before you send a TX (more than just syncing) this allows it to collect enough other TX to make a good judgement on how high the fee should be.

Hope this doesn't take forever, it's still unconfirmed

edit: jesus it finally confirmed, again, thanks for the info man!

in the future consider paying 0.0001

 it is about 2.6 - 2.8 cents  worth paying.

[shorena]

-snip-
Yeah, the slider was all the way to the left. The sending amount was .16.
So pretty much just keep my bitcoin core open? Thanks for your help btw.

Yes, keeping it open will make sure that your transaction does not get forgotten by the network as the client will rebroadcast it from time to time. For the future it also helps to keep the client open for a while before you send a TX (more than just syncing) this allows it to collect enough other TX to make a good judgement on how high the fee should be.

Hope this doesn't take forever, it's still unconfirmed

edit: jesus it finally confirmed, again, thanks for the info man!

in the future consider paying 0.0001

 it is about 2.6 - 2.8 cents  worth paying.

Bitcoin core is usually pretty good in determining a good enough fee adjusted to the current situation on the blockchain. It just needs so time to gather data. IIRC there is a small warning about this. Maybe it should be more prominent.

[peligro]

I tried sending BTC, but it's been at 0/unconfirmed since 9AM. It's now 12PM. I included a tax fee of 0.00000591 BTC. Is this normal? Is there any way to speeding this up?

I'm using bitcoin core

At that time another spam attack on the blockchain happened. Your fee was so low that all the spam transactions had a higher fee and your transaction did not get included into a block. Which means no confirmations happened.

In the future, check out this website before sending a transaction: http://www.cointape.com/

It tells you if an attack is going on and which fee you would need to have your transaction confirmed.

It's not a great solution but at least a solution until a better solution is found against those spammers.

[shorena]

I tried sending BTC, but it's been at 0/unconfirmed since 9AM. It's now 12PM. I included a tax fee of 0.00000591 BTC. Is this normal? Is there any way to speeding this up?

I'm using bitcoin core

At that time another spam attack on the blockchain happened. Your fee was so low that all the spam transactions had a higher fee and your transaction did not get included into a block. Which means no confirmations happened.

In the future, check out this website before sending a transaction: http://www.cointape.com/

It tells you if an attack is going on and which fee you would need to have your transaction confirmed.

It's not a great solution but at least a solution until a better solution is found against those spammers.

The client (bitcoin core) used by OP has a solution, there is no need for a 3rd party website that is not even working without java script and happily shares all your info with google.