unconfirmed transaction

[btctoo]

My bitcoin transaction is still unconfirmed, which is making a series of transaction unconfirmed

tx1: https://www.blockchain.com/btc/tx/ab3f0402ca623c8f53fe195f70a26eaf966ff0d9d9bacda3f3f6cddea906d428 - 24 hrs - same addr to same addr [by mistake]
tx2: https://www.blockchain.com/btc/tx/640a3af209074680f5cb542db3f647bb79a9c51972f83c17680d13664c8b06ef
tx3: https://www.blockchain.com/btc/tx/75cce43c0369db9579382b9f46b43de3be68a8579517d0c618cad2862ccb4a2a
tx4: https://www.blockchain.com/btc/tx/893b9d88dc8283844c15d43b6dd198a313dfcfe7736df9c43863f35e29bc89de - same addr to same address

I had accelerated the first transaction, for free throrugh btcstrike

Please guide

[1714005623]

1714005623

[1714005623]

1714005623

[1714005623]

1714005623

[jackg]

What software are you using, do you have a possibility to pump the fee if you right click the transaction (or look at the transaction details).

I'd suggest bumping the first to 20-50 sats per byte and see if that helps it confirm if you can, if not you'll proabably have to calculate the difference and do a CFPF but i'm not sure how far back miner's clients will go to check this...

[Rath_]

I'd suggest bumping the first to 20-50 sats per byte

20-50 sat/byte is way too much. 12-14 sat/byte should be enough for now to get any transaction confirmed in the next few blocks. The mempool cleared itself significantly in the last 24 hours. His first transaction (~10 sat/byte fee) should get confirmed soon.

[DaveF]

Looking at https://mempool.space/ BitCryptex is correct. 10 sats / byte should clear soon baring some horrific variance.

Sometimes I wish there was a best estimated rate to clear in the next 1 / 5 / 10 / 144 blocks on the top of the support forum. Would save a step in going elsewhere to check.

Stay safe.

-Dave

[btctoo]

i have blockchainwallet

[Rath_]

i have blockchainwallet

Then you can't use RBF (replace-by-fee). The only thing you can do is spending those unconfirmed coins again (if possible; you can even send them to yourself again) with a higher fee than the original transaction - it is called CPFP (Child Pays For Parent). If you don't need those coins to confirm urgently then you should wait. The mempool is clearing up.

[hosseinimr93]

What software are you using, do you have a possibility to pump the fee if you right click the transaction (or look at the transaction details).

None of the transactions made by OP are RBF.
if a transaction is RBF, Blockstream explorer shows its status as UNCONFIRMED (RBF).

For example this transaction which was made by OP is not RBF.

[btctoo]

i have blockchainwallet

Then you can't use RBF (replace-by-fee). The only thing you can do is spending those unconfirmed coins again (if possible; you can even send them to yourself again) with a higher fee than the original transaction - it is called CPFP (Child Pays For Parent). If you don't need those coins to confirm urgently then you should wait. The mempool is clearing up.

Can you guide how i do that

[o_e_l_e_o]

Can you guide how i do that

First you need to figure out what you are trying to achieve. You have sent a variety of coins from a variety of addresses to the 1pixedi... address, but then you've split one of the inputs at that address in to two inputs, both going to the same address. This makes no sense. If anything, it is the exact opposite of what you want to do, which is to consolidate all your inputs in to one. There is no point in splitting coins in to multiple outputs at the same address.

If you want to confirm all your transactions, then you need to make a transaction which spends everything at the 1pixedi... address, and sends it to another address. However, since you have a chain of 4 unconfirmed transactions, your new fee will need to be enough to push the combined 5 transactions (the 4 old ones and the new one you are about to make) up to a high combined total fee, which will be expensive.

The combined size of your 4 unconfirmed transaction is (530 + 635 + 225 + 258) = 1638 bytes. Your new transaction of 3 legacy inputs and one legacy output is going to be 488 bytes (give or take), giving a combined total of 2126 bytes. To confirm that in the next block you are looking at a combined fee in the region of 100 sats/vbyte, which is 212,600 sats. Ignoring the fees you have paid on the previous transactions (which are a negligible total of around 10,000 sats), your new transaction will therefore need a fee of 212,600/488 = 435 sats/vbyte.

Given that you've already waited 5 hours for 2 of the transactions, and over a day for the other 2, my advice would simply be to wait longer. The mempool is gradually emptying as it tends to do at weekends, and there is a reasonable chance they will confirm within the next 6 hours or so even if you do nothing.

[logfiles]

My bitcoin transaction is still unconfirmed, which is making a series of transaction unconfirmed

tx1: https://www.blockchain.com/btc/tx/ab3f0402ca623c8f53fe195f70a26eaf966ff0d9d9bacda3f3f6cddea906d428 - 24 hrs - same addr to same addr [by mistake]

The first transaction got confirmed some 30 minutes ago but the second transaction fee is very low at 2 sats/vByte. You may have to wait for a while again until it gets confirmed too.
Remember the first one that took over 1 day and 16 hrs and  just got confirmed was at 9.98 sats/vByte

[joniboini]

You might want to change your wallet so you can do RBF. Sacrifice some convenience for more control over your transactions. Electrum is a popular choice and I believe you can do some extensive research on this topic on your own.

[nc50lc]

I had accelerated the first transaction, for free throrugh btcstrike

If you're using btcstrike, try to accelerate all of them. not just the first (BTW, the 1st was confirmed).
I already did.

They will accept any transaction regardless of low fee rate or unconfirmed parent transaction;
but it's not guaranteed as they say.

[btctoo]

Can you guide how i do that

First you need to figure out what you are trying to achieve. You have sent a variety of coins from a variety of addresses to the 1pixedi... address, but then you've split one of the inputs at that address in to two inputs, both going to the same address. This makes no sense. If anything, it is the exact opposite of what you want to do, which is to consolidate all your inputs in to one. There is no point in splitting coins in to multiple outputs at the same address.

If you want to confirm all your transactions, then you need to make a transaction which spends everything at the 1pixedi... address, and sends it to another address. However, since you have a chain of 4 unconfirmed transactions, your new fee will need to be enough to push the combined 5 transactions (the 4 old ones and the new one you are about to make) up to a high combined total fee, which will be expensive.

The combined size of your 4 unconfirmed transaction is (530 + 635 + 225 + 258) = 1638 bytes. Your new transaction of 3 legacy inputs and one legacy output is going to be 488 bytes (give or take), giving a combined total of 2126 bytes. To confirm that in the next block you are looking at a combined fee in the region of 100 sats/vbyte, which is 212,600 sats. Ignoring the fees you have paid on the previous transactions (which are a negligible total of around 10,000 sats), your new transaction will therefore need a fee of 212,600/488 = 435 sats/vbyte.

Given that you've already waited 5 hours for 2 of the transactions, and over a day for the other 2, my advice would simply be to wait longer. The mempool is gradually emptying as it tends to do at weekends, and there is a reasonable chance they will confirm within the next 6 hours or so even if you do nothing.

Tx for your advice, id prefer to wait more

[HCP]

Tx for your advice, id prefer to wait more

You could potentially be waiting for quite a while (as in hours if not days):


There are currently some 30+ blocks worth of transactions all sitting at the 2+ sats/byte type fee range... which is about what your #2 & #3 transactions were set to... #4 is higher, but is effectively a CPFP of #3 (which was quite big at 635 bytes)... so with #4 being 258 bytes... the combined size is 893 bytes with a combined fee of 0.00002528 + 0.00003375 = 0.00005903... which only gives ~6 sats/byte... or 1.5 sats/WU.

If you're really lucky, and it stays "quiet" and there aren't many more transactions broadcast... #3 and #4 might confirm in the next hour or so... but #2 could stay unconfirmed for quite a bit longer!

[Sanitough]

There are still a lot of transaction that is still unconfirmed now, I am not an expert but I'd like to share since we have the same experience.
I have transacted 2 days ago if I am not mistaken, I choose a cheap transaction fee and it was not confirm for days already so I just increase the transaction fee, I think I needed to pay like 4 usd of that certain transaction just to get confirmed, by the way, I am using electrum wallet.

[btctoo]

Tx for your advice, id prefer to wait more

You could potentially be waiting for quite a while (as in hours if not days):
https://i.imgur.com/ZcM4s2h.png

There are currently some 30+ blocks worth of transactions all sitting at the 2+ sats/byte type fee range... which is about what your #2 & #3 transactions were set to... #4 is higher, but is effectively a CPFP of #3 (which was quite big at 635 bytes)... so with #4 being 258 bytes... the combined size is 893 bytes with a combined fee of 0.00002528 + 0.00003375 = 0.00005903... which only gives ~6 sats/byte... or 1.5 sats/WU.

If you're really lucky, and it stays "quiet" and there aren't many more transactions broadcast... #3 and #4 might confirm in the next hour or so... but #2 could stay unconfirmed for quite a bit longer!

The second transaction has been confirmed, and so are other being confirmed, thanks all for your supportt

[asianguy845]

My bitcoin transaction is still unconfirmed, which is making a series of transaction unconfirmed

tx1: https://www.blockchain.com/btc/tx/ab3f0402ca623c8f53fe195f70a26eaf966ff0d9d9bacda3f3f6cddea906d428 - 24 hrs - same addr to same addr [by mistake]
tx2: https://www.blockchain.com/btc/tx/640a3af209074680f5cb542db3f647bb79a9c51972f83c17680d13664c8b06ef
tx3: https://www.blockchain.com/btc/tx/75cce43c0369db9579382b9f46b43de3be68a8579517d0c618cad2862ccb4a2a
tx4: https://www.blockchain.com/btc/tx/893b9d88dc8283844c15d43b6dd198a313dfcfe7736df9c43863f35e29bc89de - same addr to same address

I had accelerated the first transaction, for free throrugh btcstrike

Please guide

An easy thing to do would be to contact a moderator/admin/helper on your receiving wallet.
My brother had the same problem, and then after a month of waiting, he finally contacted the admins on the receiving wallet, and then he had the bitcoin immediately. You should do the same, it should work.

[ranochigo]

An easy thing to do would be to contact a moderator/admin/helper on your receiving wallet.
My brother had the same problem, and then after a month of waiting, he finally contacted the admins on the receiving wallet, and then he had the bitcoin immediately. You should do the same, it should work.

The only thing the owner of the receiving address could do is to execute a CPFP transaction which could incur an extra fee. If its an automated system, they probably won't bother helping you at all. The fact that your brother waited a month probably means that the mempool also coincidentally cleared up.