It will take very long time to confirm a tx like this.
No tx fee... no miner is willing to pack your transaction in their mined block.
You should always add a small fee, man
Topic: unconfirmed transactions - page 2. (Read 2930 times)
Oh there you go the transaction has been dropped https://blockchain.info/en/tx/f24ff339fc651b0b28cdfc0e67bb4c2f91b46cbd39935ff4d70c95bb5c33b0e9 it says "Transaction not found" I recommend you to resend the coins now with a fee as some nodes might rebroadcast it(it happened once with me transaction got dropped and I decided to not resend it next day it was rebroadcast even though I have never opened my client)
It appears to be rebroadcasted again. Even if you don't open the client but the client behaviour is to rebroadcast after the transaction falls out of the mempool, it will still automatically broadcast. In this case, even though no node is relaying it right now due to its low fee (https://blockchain.info/inv/f24ff339fc651b0b28cdfc0e67bb4c2f91b46cbd39935ff4d70c95bb5c33b0e9) the transaction appeared to have been stored in Blockchain.info's mempool again. The only way now is to either doublespend it or just wait for it to confirm, it will confirm eventually but it takes a long time.OP, you should also contact the receiver (if you are just the sender) and ask him not to rebroadcast the transaction. Otherwise, the receiver may keep rebroadcasting it again and again.
Consider to send your transactions with a fee of 0.00000001 (one satoshi) instead of none fee.
Sorry, that's nonsense. Either leave out the fee (and risk that the transaction won't be processed) or add the standard fee of 0.0001 BTC to ensure that everything works as it should.
Miners that refuse to process no-fee transactions would most likely refuse one-satoshi transations as well.
Onkel Paul
Yup ranochigo and Onkel is right.
AFAIK, transactions with at least min fee are ranked by pools by tx fee per byte.
And for transaction with less than min fee, they are ranked by the priority:
Code:
priority = sum(input_value_in_base_units * input_age)/size_in_bytes
Consider to send your transactions with a fee of 0.00000001 (one satoshi) instead of none fee.
Sorry, that's nonsense. Either leave out the fee (and risk that the transaction won't be processed) or add the standard fee of 0.0001 BTC to ensure that everything works as it should.
Miners that refuse to process no-fee transactions would most likely refuse one-satoshi transations as well.
Onkel Paul
i dont think theres anything to worry, since its already sent.
There are few things to worry about 1.It could be rebroadcast over and over again thus taking months to confirm. 2.It could never confirm(drops from memory pool(applies only for the receiver).Consider to send your transactions with a fee of 0.00000001 (one satoshi) instead of none fee.
Sorry, that's nonsense. Either leave out the fee (and risk that the transaction won't be processed) or add the standard fee of 0.0001 BTC to ensure that everything works as it should.
Miners that refuse to process no-fee transactions would most likely refuse one-satoshi transations as well.
Onkel Paul
i dont think theres anything to worry, since its already sent.
There are few things to worry about 1.It could be rebroadcast over and over again thus taking months to confirm. 2.It could never confirm(drops from memory pool(applies only for the receiver). It appears to be rebroadcasted again. Even if you don't open the client but the client behaviour is to rebroadcast after the transaction falls out of the mempool, it will still automatically broadcast. In this case, even though no node is relaying it right now due to its low fee (https://blockchain.info/inv/f24ff339fc651b0b28cdfc0e67bb4c2f91b46cbd39935ff4d70c95bb5c33b0e9) the transaction appeared to have been stored in Blockchain.info's mempool again. The only way now is to either doublespend it or just wait for it to confirm, it will confirm eventually but it takes a long time.
Here's a question that's not too far off-topic: what if you suggest an amount *greater than* the 0.0001 or so BTC that's recommended? Does it mean instead of waiting say 1 hour you would wait a lot less, if your reward for confirm is greater? And how much faster would the confirm be? Double the amount means half the time to confirm? Or I guess it varies on the network congestion at any give time?
i dont think theres anything to worry, since its already sent.
hero member
Activity: 560
Merit: 509
I prefer Zakir over Muhammed when mentioning me!
It appears to be rebroadcasted again. Even if you don't open the client but the client behaviour is to rebroadcast after the transaction falls out of the mempool, it will still automatically broadcast. In this case, even though no node is relaying it right now due to its low fee (https://blockchain.info/inv/f24ff339fc651b0b28cdfc0e67bb4c2f91b46cbd39935ff4d70c95bb5c33b0e9) the transaction appeared to have been stored in Blockchain.info's mempool again. The only way now is to either doublespend it or just wait for it to confirm, it will confirm eventually but it takes a long time.
Here's a question that's not too far off-topic: what if you suggest an amount *greater than* the 0.0001 or so BTC that's recommended? Does it mean instead of waiting say 1 hour you would wait a lot less, if your reward for confirm is greater? And how much faster would the confirm be? Double the amount means half the time to confirm? Or I guess it varies on the network congestion at any give time?
It isn't really like that. But the priority will be higher, so it will be confirmed faster but we can't say the correct time.
~~MZ~~
It appears to be rebroadcasted again. Even if you don't open the client but the client behaviour is to rebroadcast after the transaction falls out of the mempool, it will still automatically broadcast. In this case, even though no node is relaying it right now due to its low fee (https://blockchain.info/inv/f24ff339fc651b0b28cdfc0e67bb4c2f91b46cbd39935ff4d70c95bb5c33b0e9) the transaction appeared to have been stored in Blockchain.info's mempool again. The only way now is to either doublespend it or just wait for it to confirm, it will confirm eventually but it takes a long time.
Here's a question that's not too far off-topic: what if you suggest an amount *greater than* the 0.0001 or so BTC that's recommended? Does it mean instead of waiting say 1 hour you would wait a lot less, if your reward for confirm is greater? And how much faster would the confirm be? Double the amount means half the time to confirm? Or I guess it varies on the network congestion at any give time?
Oh there you go the transaction has been dropped https://blockchain.info/en/tx/f24ff339fc651b0b28cdfc0e67bb4c2f91b46cbd39935ff4d70c95bb5c33b0e9 it says "Transaction not found" I recommend you to resend the coins now with a fee as some nodes might rebroadcast it(it happened once with me transaction got dropped and I decided to not resend it next day it was rebroadcast even though I have never opened my client)
It appears to be rebroadcasted again. Even if you don't open the client but the client behaviour is to rebroadcast after the transaction falls out of the mempool, it will still automatically broadcast. In this case, even though no node is relaying it right now due to its low fee (https://blockchain.info/inv/f24ff339fc651b0b28cdfc0e67bb4c2f91b46cbd39935ff4d70c95bb5c33b0e9) the transaction appeared to have been stored in Blockchain.info's mempool again. The only way now is to either doublespend it or just wait for it to confirm, it will confirm eventually but it takes a long time. 
Consider to send your transactions with a fee of 0.00000001 (one satoshi) instead of none fee.
Sorry, that's nonsense. Either leave out the fee (and risk that the transaction won't be processed) or add the standard fee of 0.0001 BTC to ensure that everything works as it should.
Miners that refuse to process no-fee transactions would most likely refuse one-satoshi transations as well.
Onkel Paul
Consider to send your transactions with a fee of 0.00000001 (one satoshi) instead of none fee.
Oh there you go the transaction has been dropped https://blockchain.info/en/tx/f24ff339fc651b0b28cdfc0e67bb4c2f91b46cbd39935ff4d70c95bb5c33b0e9 it says "Transaction not found" I recommend you to resend the coins now with a fee as some nodes might rebroadcast it(it happened once with me transaction got dropped and I decided to not resend it next day it was rebroadcast even though I have never opened my client)
Transactions without fee may be long, several miners are choosing blocks with higher fee.
Has it occurred to me that a transaction without fee delay 4 days to confirm.
Has it occurred to me that a transaction without fee delay 4 days to confirm.
so just keep waiting? 
You just have to wait. It'll get confirmed in due time. Always best to include a fee to keep things moving along.
What happens if a node continuously pumps dust into the blockchain? Like a server farm of 100s of PCs that do nothing but pump dust into the BTC blockchain, in an attempt to cripple it like a DOS attack? Does that node get somehow cut off?
You just have to wait. It'll get confirmed in due time. Always best to include a fee to keep things moving along.
What happens if a node continuously pumps dust into the blockchain? Like a server farm of 100s of PCs that do nothing but pump dust into the BTC blockchain, in an attempt to cripple it like a DOS attack? Does that node get somehow cut off?
In the past people have done that but it would cost them alot in fees. Or they would get rejected.
You just have to wait. It'll get confirmed in due time. Always best to include a fee to keep things moving along.
What happens if a node continuously pumps dust into the blockchain? Like a server farm of 100s of PCs that do nothing but pump dust into the BTC blockchain, in an attempt to cripple it like a DOS attack? Does that node get somehow cut off?
Jump to: