Thank you so much for your time in responding! I can't believe I never realized that my transaction leading to the subsequent transactions would affect the subject transaction. That is fascinating. I have always bragged on behalf of my favorite wallet, copay, for their allowance of spending unconfirmed funds. Is this a show of smoke and mirrors? Are they claiming to do the impossible? Thanks so much for writing back!
Spending from unconfirmed funds is generally ill-advised because it can cause situations like the one you are currently stuck in. However, it is not impossible to spend from a unconfirmed transactions, but it also is not as safe or as user friendly as spending from confirmed transactions. 
Topic: Perhaps I will sound like a broken record, but this is baffling! (Read 397 times)
Hummm, usually a wallet lets you only spend coins which have already some
confirmations. Eg multibit has two balances: "Balance" and "Balance ready to
spend" (or something alike). And now it seems like a good idea that multibit
does it that way..
confirmations. Eg multibit has two balances: "Balance" and "Balance ready to
spend" (or something alike). And now it seems like a good idea that multibit
does it that way..
Your "slow" transaction has nothing to do with the transaction fee and everything to do with the fact that it is spending from a chain of unconfirmed transactions. Your transaction cannot confirm until the unconfirmed transactions that it spends from confirm as well, and that chain is being held up by https://blockchain.info/tx/8f53d15494c71036ffae716e63402d68cf49524f42561b02c226738cc1fba277 which pays a low transaction fee.
Also, the absolute value of your fee does not matter, and how that is related to previous transactions matters even less. What matters is the fee rate in BTC/kB, which your transaction sufficiently covers.
Also, the absolute value of your fee does not matter, and how that is related to previous transactions matters even less. What matters is the fee rate in BTC/kB, which your transaction sufficiently covers.
Thank you so much for your time in responding! I can't believe I never realized that my transaction leading to the subsequent transactions would affect the subject transaction. That is fascinating. I have always bragged on behalf of my favorite wallet, copay, for their allowance of spending unconfirmed funds. Is this a show of smoke and mirrors? Are they claiming to do the impossible? Thanks so much for writing back!
Your "slow" transaction has nothing to do with the transaction fee and everything to do with the fact that it is spending from a chain of unconfirmed transactions. Your transaction cannot confirm until the unconfirmed transactions that it spends from confirm as well, and that chain is being held up by https://blockchain.info/tx/8f53d15494c71036ffae716e63402d68cf49524f42561b02c226738cc1fba277 which pays a low transaction fee.
Also, the absolute value of your fee does not matter, and how that is related to previous transactions matters even less. What matters is the fee rate in BTC/kB, which your transaction sufficiently covers.
Also, the absolute value of your fee does not matter, and how that is related to previous transactions matters even less. What matters is the fee rate in BTC/kB, which your transaction sufficiently covers.
I am sure everyone is rolling their eyes about all the slow blockchain topics. This one is baffling though, because twice it has returned results saying "transaction does not exist" or "transaction not found" . My fee paid is .0006 btc which is 3 times the cost regularly and yet my transaction still is somewhere in the bottom of the mining pits of doom. I wish I could start my own mining project! I would name it "Bottom Feeders Inc." and its sole goal would be to take a fee to scan and scrape the bottom of the pools for lost and forgotten transactions whose senders are bewildered and tired of waiting. I wish it was actually possible. Any insights into this goofy transaction would rock my world. Here is transaction ID.
22c75fe951896317a2d1335df8ee5ae28b22cb0b10a506127dd91afb20fc94ff
*Edited to fix a typo*🤓
22c75fe951896317a2d1335df8ee5ae28b22cb0b10a506127dd91afb20fc94ff
*Edited to fix a typo*🤓
Jump to: