Unconfirmed Tsx please someone help.

[NeuroticFish]

lock time: 679494

am i need to wait 679494 blocks if its unconfirmed?

No. Until block 679494. But you should not worry about it, it has already passed, last block was already 679711

[hosseinimr93]

is it possible to upgrade for this unconfirmed tsx to segWit-Bech32?

No.
It's recommended to hold your coins in segwit addresses to pay lower fee when you make a transaction. As your fund is now in a legacy address (an address starting with 1), there is no way to benefit the discount.
From now on, try to use segwit addresses for holding your bitcoin.

There are two types of segwit addresses.
1. Native segwit (Bech32): addresses starting with bc1
2. Nested segwit (P2SH): addresses starting with 3*

*Just note that not all addresses starting with 3 are segwit. Multisig addresses start with 3 as well.

[uaaeu]

how many days should i wait for dropping from mempool if my tsx still unconfirmed

[o_e_l_e_o]

is it possible to upgrade for this unconfirmed tsx to segWit-Bech32?

No. You have to create a brand new segwit wallet and move all your coins to it to take advantage of the lower fees segwit provides.

am i need to wait 679494 blocks if its unconfirmed?

No. The locktime is the earliest block which can include your transaction. Since we have already passed block 679,494, your transaction is free to be included in a block.

how many days should i wait for dropping from mempool if my tsx still unconfirmed

Provided you do not rebroadcast your transaction, it will be removed from default mempools either when the mempool size limit is filled with transactions paying a higher fee and your transaction is purged from the bottom, or after 14 days.

[Chikito]

how many days should i wait for dropping from mempool if my tsx still unconfirmed

have you broadcasted yet?.

since happen to local (clicked - advance feature fee), I am not sure you going to that.



after a sign, you should also click a broadcast button.

[nc50lc]

i removed it when i see. its removed and my money is back but when i checked it again it turns unconfirmed again why?

In contrary with the previous posts, your "unconfirmed" transaction turned "local" is because your selected server's node had purged your transaction from their mempool due to prioritizing txns with higher fee rates.
Then it returned to your wallet after either auto-connecting to a different server that has your transaction or it was re-accepted by their node.

70sat/vB is good enough IMO if you're not in a hurry. It's just because the average mempool is absurdly too high right now that a txn with good fee rate like that got stuck.
You can also try to accelerate it using ViaBTC's free accelerator, send it to them at exactly HH:00 in the clock.