Can you explain a bit what you meant by priority of 57,000,000... transactions with priority over 57,600,000 are free. that means no fee required. though in real practice it may still take time to confirm. |
|
|
|
I actually did not send the transaction , its beening sent to me. Is it an easy thing to do to increase the fee of an existing unconfirmed Transaction ?
there's two ways. one makes it return to the sender's wallet and the other will need the sender to double spend it. basically it's up to the sender. you can only wait. |
|
|
|
how do we know he didn't mine a lot of BTC to an unknown address during the early days and is spending them gradually?
Check: https://bitslog.wordpress.com/2013/04/17/the-well-deserved-fortune-of-satoshi-nakamoto/Disclaimer: I can’t assure with 100% certainty that the all the black dots are owned by Satoshi, but almost all are owned by a single entity, and that entity began mining right from block 1, and with the same performance as the genesis block. It can be identified by constant slope segments that occasionally restart. Also this entity is the only entity that has shown complete trust in Bitcoin, since it hasn’t spend any coins (as last as the eye can see). I estimate at eyesight that Satoshi fortune is around 1M Bitcoins, or 100M USD at current exchange rate. I’m sure there will be plenty of people that will carefully analyze the source data set and come up with the exact figure, which will be very close, but nevertheless they will scream at me again. still can't prove that satoshi didn't mine using other computer(s) around that time. plus gmaxwell and theymos claimed that they and many people they know of mined around that time. maybe satoshi did mine most of those blocks and never planned to spend it because he had some concern of what so many bitcoins can do to its economic growth. but did mine a safe amount of bitcoin using other separate computer(s) for himself. |
|
|
|
|
how do we know he didn't mine a lot of BTC to an unknown address during the early days and is spending them gradually?
|
|
|
|
Probably because you are using funds that aren't confirmed in the first place.
That may be caused because you don't know what you're doing or because you are using a bad wallet like blockchain.info
the inputs got confirmed a day ago though. so that's not it. afaik that tx have no problem except for the part that it was sent in the middle of a unconfirmed transaction traffic jam. |
|
|
|
both transaction have very low fees. plus the second tx spends an input from the first one so it won't get confirmed before the first tx. plus the mempool is flooding like crazy... so your tx might not get confirmed at all. Is there anything I can do to get the coins back or am I SOL?
you can wait for the mempool to drop your tx. it'll get returned to your wallet then. probably will take two to three days. |
|
|
|
I sent 0.1btc which (according to my wallet) is 224bytes. Based on your 20satoshi per byte im almost double that.
I may just send the transaction again with a 0.0003 fee and see if that makes any difference. Ive got enough to cover it in my wallet so wont be double spending it but obviously don't want to lose the 0.1 I sent in the first place.
that should be enough to get your tx through. it shouldn't take long unless the tx spends an input from an unconfirmed transaction. |
|
|
|
okay this got to be the 10th topic about unconfirmed transaction I've replied to today. I'll quote my reply from the other thread. because the mempool is flooded with unconfirmed transactions. call it a traffic jam, and the ones with higher tx fees can get through faster.  to know how much fee per byte are best for the current traffic condition, use this site.
btw your tx will get confirmed eventually. |
|
|
|
Hi guys,
Having only recently sent my first btc I included a few of 0.0001 to the transaction. Is this enough or should it be more?
If it's not enough and the transaction is stuck what happens next?
Thanks.
depends. if you're paying .0001 for a 250~ byte transaction then it is good enough. it may take some time if you sent a 1KB tx with the standard .0001 fee. the optimal fee right now is 20 satoshi per byte/.0002 per KB (or more if you want it to get confirmed quickly. best is 50-60 satoshi per byte). if the tx never get confirmed it'll return to your wallet after all node stop relaying it across the network (if you're using core you need to delete the tx first.). |
|
|
|
you just sent that tx like 10 minutes ago, dude. have patience.  This. The last block found was at 2016-02-29 21:28:41. The transaction was broadcasted at 2016-02-29 21:51:59. A block has not yet been found, so the transaction cannot yet be confirmed. I would guess that the transaction will be included in the next block. do you mean it's not going to be confirmed next 5 hours? what can i do? actually i'm little hurry because my site funds about to be empty  no 5 hours is waaay too long. shouldn't take more than a hour. hell a new block may have been founded while I'm typing this. |
|
|
|
you just sent that tx like 10 minutes ago, dude. have patience. can't comment on your other txes because you didn't post them. |
|
|
|
So you think the mem pool has to clear before this goes through ?
no. you just need a little luck (or a miner.). that tx have 0.002 fee (around 10 sat per byte. a bit low but not too low.) so I doubt you'll have to wait for too long. and the priority will increase as the inputs get more confirmation. |
|
|
|
not looking good. that tx have a huge size (19KB!!) you'll probably not get your btc anytime soon. if it takes too long, you can choose make the mempool drop the tx so that it'll return to your wallet. but that also takes time. edit:
if it makes you feel better. two weeks ago someone sent a 8kb tx with .0001 fee and it got confirmed in about a day ( thread). iirc the mempool was slightly flooded too back then but not as bad as now.
Most likely answers you get are: 1) fee to low, 2) its it a spam transaction, 3) your tx depends on confirming previous unconfirmed transactions \s
still better than guessing wildly without even knowing what the problem there is. I doubt you even clicked the link. |
|
|
|
|
no idea (anyone knows?).
but even if they should help speed things up your tx have a fairly low fee and dust output.
|
|
|
|
|
of course it have 0 priority. the input is zero confirmation old (unconfirmed). happens to a lot of people.
|
|
|
|
Hi,
Why Bitcoin transactions are so slow to get confirmed today?
because the mempool is flooded with unconfirmed transactions. call it a traffic jam, and the ones with higher tx fees can get through faster. to know how much fee per byte are best for the current traffic condition, use this site. |
|
|
|
Thanks. I heard you can try to resend with a higher fee and it'll process the original and reject the 2nd attempt, is that correct or have I misunderstood?
well, it's called a race attack (a kind of double spend) so either one can be processed with right condition. you can successfully double spend if you have some help from a node and/or a miner. Oh and how can I check if the network has dropped the transaction?
check blockchain.info and other block explorers for your tx. if they're not there then your tx is no longer in their mempool. then you can broadcast a new transaction to their node using the same inputs. |
|
|
|
Congrats to Cyrus, do we know what is the number of total of Global moderators and which are?
5 grue, SaltySpitoon, hilariousandco, badbear_away, Cyrus. looks like some other global mod (raoul duke, maged, malevolent(?)) is no longer staff. |
|
|
|
It's weird, the 2nd transaction is high priority but I haven't changed anything....
that's because the priority is calculated from the amount of bitcoin sent and input age and transaction size. so an unconfirmed tx gets more priority as the input gets more confirmation (more old). Thanks.c Ok my wallet has reloaded and the two transactions have disappeared and my available balance has gone back up, what happens now lol. Should I re-send or... not now. it won't work because it'll be rejected as double spend. wait for the mempool to drop your tx completely before resending bitcoins using the same inputs as those transactions. this may take up to 3 days. |
|
|
|
It's weird, the 2nd transaction is high priority but I haven't changed anything....
that's because the priority is calculated from the amount of bitcoin sent and input age and transaction size. so an unconfirmed tx gets more priority as the input gets more confirmation (more old). |
|
|
|
|
Show Posts
