|
Title: TX not confirming @106 fee, can I speed it up somehow? Post by: dadach on December 21, 2017, 12:15:44 PM So this tx is not confirming, and then subsequently another one @200, and another @732...
The initial tx info is here, if you got after spent you will see the other two. https://blockchain.info/tx/fc1b864799a602690812d4383f1b80a6a8ef19eaf947f6d5116f8861bc9b90eb the tx were initialized from ledger nano s and mycellium. what should i expect here, as i see some lower fee transactions get confirmed all the time in the new blocks, and they were issued this morning... can i speed it up? will i lose all the btc involved? thanks for the info :) Title: Re: TX not confirming @106 fee, can I speed it up somehow? Post by: buwaytress on December 21, 2017, 01:19:06 PM I guess you'll know by now the mempool has been bloating up, with no end in sight. I've experienced several congestion periods this year, but probably none as extended as this. Check out this estimator to have an idea of how long your txs will take to confirm :https://bitcoinfees.earn.com/
These estimates will only increase as mempool grows, they will also come down if the network eases up. So, are current levels, any tx with a fee below 401 sats/byte (!), expect them never to confirm unless mempool comes down. At 732 sats/byte, if the situation holds, you'll get a 90% chance of confirmation within the next 5 hours, so I think you're "safe" on that. BUT, since the higher fee needs the preceding 2 txs to confirm first (since it spends unconfirmed outputs in a string of 3 txs)... you've no choice but to wait for the earlier ones to confirm. Your options now are to attempt a CPFP, making one more transaction using the same linked outputs, including fees to pay for all. Mycelium should support it, though I'm not sure if you can link 3... essentially, you're doing a child pays for parent and grandparent ;) Or, more painstakingly, seek help from an acceleration service to confirm the 1st, then second. You can keep trying yourself on the hour every hour, submitting to https://pool.viabtc.com/tools/txaccelerator/ but you're going to have to get lucky as they only accept 100 every hour. Try about 5 mins before the hour. Title: Re: TX not confirming @106 fee, can I speed it up somehow? Post by: dadach on December 21, 2017, 05:46:10 PM I guess you'll know by now the mempool has been bloating up, with no end in sight. I've experienced several congestion periods this year, but probably none as extended as this. Check out this estimator to have an idea of how long your txs will take to confirm :https://bitcoinfees.earn.com/ These estimates will only increase as mempool grows, they will also come down if the network eases up. So, are current levels, any tx with a fee below 401 sats/byte (!), expect them never to confirm unless mempool comes down. At 732 sats/byte, if the situation holds, you'll get a 90% chance of confirmation within the next 5 hours, so I think you're "safe" on that. BUT, since the higher fee needs the preceding 2 txs to confirm first (since it spends unconfirmed outputs in a string of 3 txs)... you've no choice but to wait for the earlier ones to confirm. Your options now are to attempt a CPFP, making one more transaction using the same linked outputs, including fees to pay for all. Mycelium should support it, though I'm not sure if you can link 3... essentially, you're doing a child pays for parent and grandparent ;) Or, more painstakingly, seek help from an acceleration service to confirm the 1st, then second. You can keep trying yourself on the hour every hour, submitting to https://pool.viabtc.com/tools/txaccelerator/ but you're going to have to get lucky as they only accept 100 every hour. Try about 5 mins before the hour. thank you for your help. so when i try to do CPFP, it says unable to bump transaction...is there anything to do manually? also, when would the tx expire if thats even possible. there is an option for - delete unconfirmed transaction. |