Pages:
Author

Topic: Stuck in mempool @ 17.9 for 2 weeks - page 2. (Read 374 times)

legendary
Activity: 2226
Merit: 1172
Privacy Servers. Since 2009.
November 24, 2023, 04:36:08 PM
#8
I have a similar situation but a bit higher fee. Still my transaction has been sitting in the mempool for like two weeks or so. ViaBTC refuses to accelerate my transaction as they seem to have some size limit and my transaction obviously exceeds that limit. Any suggestions?

P.S. I'm not going to do RBF because I refuse to fuel this monkey token craziness. This is not an emergency, so I can wait.  Cool
legendary
Activity: 4102
Merit: 7765
'The right to privacy matters'
November 16, 2023, 11:26:18 PM
#7
I tried to check the TXID you provided above the transaction was made 2 weeks ago and the transaction was already rejected by other nodes so you should be able to recreate a new transaction I don't think CPFP will work you need to contact the sender Mia if the sent amount is already rejected or if it's funded back to her account. Ask her to make a new transaction once again with enough fee if it was already rejected.
He should let ViaBTC mine a block and the transaction would be confirmed.

I was unable to check it from blockchair.com, but I saw it on https://www.blockchain.com/explorer and https://blockstream.info.

https://blockstream.info/tx/3fc2ebf7dd2ce21a8b7a68545942c0d1b8f0f141f8a4c91865031eb65a5e4209
https://www.blockchain.com/explorer/transactions/btc/3fc2ebf7dd2ce21a8b7a68545942c0d1b8f0f141f8a4c91865031eb65a5e4209

Which means it has not been dropped from nodes of some mempool and also not displayed to be invalid on ViaBTC accelerator and can still be confirmed and it will not take up to 4 to 5 hours before ViaBTC will mine the next block.

The mempool is over 170 sat/vbyte and not worth to rebroadcast the coins. Also the sender's wallet is not his, although I doubt if it is from a custodial wallet as it is of low fee and also supporting replace-by-fee.

Edit:
ViaBTC mined block 817095 and the transaction has been confirmed.

you did good work. at op try to get a trezor.io wallet hardware and use rbf to fix issues.
legendary
Activity: 1512
Merit: 4795
November 16, 2023, 08:33:33 PM
#6
I tried to check the TXID you provided above the transaction was made 2 weeks ago and the transaction was already rejected by other nodes so you should be able to recreate a new transaction I don't think CPFP will work you need to contact the sender Mia if the sent amount is already rejected or if it's funded back to her account. Ask her to make a new transaction once again with enough fee if it was already rejected.
He should let ViaBTC mine a block and the transaction would be confirmed.

I was unable to check it from blockchair.com, but I saw it on https://www.blockchain.com/explorer and https://blockstream.info.

https://blockstream.info/tx/3fc2ebf7dd2ce21a8b7a68545942c0d1b8f0f141f8a4c91865031eb65a5e4209
https://www.blockchain.com/explorer/transactions/btc/3fc2ebf7dd2ce21a8b7a68545942c0d1b8f0f141f8a4c91865031eb65a5e4209

Which means it has not been dropped from nodes of some mempool and also not displayed to be invalid on ViaBTC accelerator and can still be confirmed and it will not take up to 4 to 5 hours before ViaBTC will mine the next block.

The mempool is over 170 sat/vbyte and not worth to rebroadcast the coins. Also the sender's wallet is not his, although I doubt if it is from a custodial wallet as it is of low fee and also supporting replace-by-fee.

Edit:
ViaBTC mined block 817095 and the transaction has been confirmed.
legendary
Activity: 3234
Merit: 2943
Block halving is coming.
November 16, 2023, 08:07:15 PM
#5
I tried to check the TXID you provided above the transaction was made 2 weeks ago and the transaction was already rejected by other nodes so you should be able to recreate a new transaction I don't think CPFP will work you need to contact the sender Mia if the sent amount is already rejected or if it's funded back to her account. Ask her to make a new transaction once again with enough fee if it was already rejected.

If this transaction is broadcasted again then you will need to wait again for 2 weeks until the transaction is rejected again by the mempool because the fee used in this transaction is around 17sat/vB which is far from the current recommended fee by mempool.space. However, you can do what hosseinimr93 suggested above if you have full control of your wallet but if it is also an exchange then you don't have any other choice but to wait again for 2 weeks
legendary
Activity: 1512
Merit: 4795
November 16, 2023, 08:04:53 PM
#4
Successfully submitted:



If ViaBTC mine the next block, the transaction will be confirmed.

You can know newly mined block here: https://mempool.space/blocks
legendary
Activity: 2380
Merit: 5213
November 16, 2023, 07:28:13 PM
#3
Do you have control over the receiving address? If so, you can do CPFP.

To do CPFP, you should spend the fund received in the unconfirmed transaction in a new transaction with a high fee.
If the fee paid for the new transaction is high enough for both transactions, miners will include them in the same block.

In the case your wallet doesn't allow you to spend unconfirmed coins, you should import your seed phrase/private key in a wallet which allow you to do so. A good option is electrum.
legendary
Activity: 1512
Merit: 4795
November 16, 2023, 07:25:23 PM
#2
The transaction support replace-by-fee, you can increase the fee.

Or you can wait for the next hour and submit the txid on ViaBTC free accelerator https://www.viabtc.com/tools/txaccelerator/ so that the transaction would be included in a block mined next by ViaBTC.

Edit:
It is from Custodial wallet, follow what hosseinimr93 posted if you can not wait and use ViaBTC accelerator. If you can wait, I can help you submit the txid in some minutes time.
newbie
Activity: 1
Merit: 0
November 16, 2023, 07:21:23 PM
#1
Hey I have a tx stuck in mempool its custodial wallet unfortunately and sender is Mia.  Please any ideas to bump fee? Or cpfp way without keys?
Tx#
3fc2ebf7dd2ce21a8b7a68545942c0d1b8f0f141f8a4c91865031eb65a5e4209

Thank you  Grin
Pages:
Jump to: