Can Bitcoin trasnaction can canceled if long time not confirmed?

[dhru9]

Someone send me $200+ few days ago
https://blockchain.com/btc/tx/55597a773941e25c9bd08c5a6aa01e9689cdfeb5b114af3da820f68722e04bd8

and not confirmed. If i keep get these transaction is this chance that it will not confirm?

[Upgrade00]

Due to spike in Bitcoin's price, the network gets more congested as more people try to get in leading to higher fees. The rate of 2.987sats/byte used for this transaction is quite small, reason why the transaction is yet to be confirmed.

If i keep get these transaction is this chance that it will not confirm?

Yes, unconfirmed transactions remain in the mempool for approximately two weeks before getting dropped if no miner picks it up, essentially they would return to the sender.
You can reach out to the sender to bump the transaction if they activated RBF or you can use CFNP~Child Pays For Parent to speed it up.

In RBF~ Replace By Fee, the sender bumps the transaction using a higher fee
In CFNP, you can send the inputs of the unconfirmed transactions to another wallet you own, using enough fees to cover for the initial transaction and the new one. A miner who wants to add your child transaction to his/her block would have to confirm the parent transaction first.

[hatshepsut93]

Yes, unconfirmed transactions remain in the mempool for approximately two weeks before getting dropped if no miner picks it up, essentially they would return to the sender.
You can reach out to the sender to bump the transaction if they activated RBF or you can use CFNP~Child Pays For Parent to speed it up.

There's no such thing as "the mempool", each node has its own mempool, and its entirely up to them how to manage it. There's no guarantee that a transaction will get or will not get dropped after a certain time, so what happens on practice, is that if you go to different explorers to check your long-stuck transactions, some will tell you that such transaction doesn't exist, while others will still see it. This unconfirmed transaction might start reappearing at any point, as some nodes that still keep it in their mempool will broadcast it again.

[Charles-Tim]

If you trust the sender, the transaction will eventually be confirmed if no manipulation, the mempool is now congested, that is the reason for many delayed transactions. But in your case, the person that send the yet unconfirmed bitcoin used a very low fee (0.00000669 BTC, 2.987 sat/byte), this fee is so low that normally it does get confirmed only during the weekend, and so far the person even send it during weekday, it will take days before it will be confirmed. But, with the congestion, it could be more than a week.

[fiulpro]

Someone send me $200+ few days ago
https://blockchain.com/btc/tx/55597a773941e25c9bd08c5a6aa01e9689cdfeb5b114af3da820f68722e04bd8

and not confirmed. If i keep get these transaction is this chance that it will not confirm?

Hello , even I have noticed the fact that transactions are taking far too long to confirm so you are not alone in this. You should actually wait for it to be confirmed or use a higher fee.

You can also boost your fee taken your wallet does have that option.

Other than that be careful that next time for sending/receiving you do use a appropriate fee , a little more does the trick.

It's just excessive network congestion these days , more people are now using bitcoins, trading, sending , receiving and therefore what we can do is : wait.

It even takes time for the transaction to be accepted into the mempool itself and after that it depends how many confirmations it would need according to your fee.

Be patient
Be careful the next time

[Upgrade00]

There's no such thing as "the mempool", each node has its own mempool, and its entirely up to them how to manage it.

Of course, nodes can personalize their mempool to have no time limit, or to a shorter one than 2 weeks. But 2 weeks (336 hours) is the default time a transaction typically lasts in a mempool, this coincides with the default mempool size of 300mb, when this is exceeded transactions gets dropped from bottom to top, i.e lower priority transactions are removed and may need to be rebroadcasted. I use 'may' cause nodes do not have to use the default settings.

This unconfirmed transaction might start reappearing at any point, as some nodes that still keep it in their mempool will broadcast it again.

I see no motivation for a node to rebroadcast an unconfirmed transaction on behalf of the sender. There are services which allows one to do this, but it usually does not help in hastening the confirmation of a transaction.