Can I send another payment if I have unconfirmed transaction?

[unfogiven19]

Hello,

Maybe due to low fees my transaction is stucked. Althogh the fees were 4$ at that time and I reduce it to 3$ .. but it is stuck.

https://www.blockchain.com/btc/tx/8df1ac38f65bce97062150fa3c9d7a019758cef829c985bd69baa9c368a91757

My question is can I send another transaction to this marketplace wallet from the same sender wallet ?

Let say I send another 10$ with regular fees to the same receipt

Will I receive the other amount too if it get confirmed ? Or it will be stuck forever.

Thank you

[o_e_l_e_o]

Let say I send another 10$ with regular fees to the same receipt

Will I receive the other amount too if it get confirmed ? Or it will be stuck forever.

The transaction will not be stuck, but it might not be credited properly.

What site or service are you depositing coins to? If they generate a single wallet address for you which never changes, then yes, you can send further transactions to that address without issue, and they will confirm quicker if you pay a higher fee.

If, however, the site or service generates an invoice or payment request for you, the address will only be monitored for a single deposit. Since you have already made a transaction to that address (although still unconfirmed), further transactions to that address may not be automatically detected by the system. Although the transaction will arrive normally, you may have to go through their customer support to get it credited to your account properly.

[NeuroticFish]

Will I receive the other amount too if it get confirmed ? Or it will be stuck forever.

First of all, don't think the fee in USD, it's useless, think ait in sat/vByte. Your tx has 24.4 sat/vbyte. The current fees are around 40-50 sat/vbyte.
If you want to spend (parts of) the rest of 0.00198082BTC, you can, depending on your wallet and settings, but keep in mind that:
* if for some reasons the first transaction is not confirmed, the second will be also remain unconfirmed
* if you put a higher-than-normal fee to the second transaction, that should make also the first transaction get confirmed faster (it's called CPFP - child pays for parent)
* since it's week-end, there's a good chance the first transaction doesn't need any help / CPFP in order to get confirmed ... today or tomorrow


If you are paying for a product and had a certain amount to pay to a one-time generated address, please be careful to what @o_e_l_e_o  said: a second tx could just cause more troubles. In such case you better discuss with the service/seller's support first.

[unfogiven19]

Hello,

Thank you all for your answers. It is a binance wallet the one that I sent money to.

[NeuroticFish]

It is a binance wallet the one that I sent money to.

Then you should be OK.

Also I noticed now, at a second look, that you have other coins/inputs in your wallet, at that address.
If you make another transaction with inputs unrelated to this unconfirmed transaction.. it's basically like you would make the transaction from another wallet. (Like you would be using a different banknote from the same wallet, although from the first banknote you didn't receive the change yet.)

[o_e_l_e_o]

It is a binance wallet the one that I sent money to.

Then yes, as NeuroticFish says, you can safely send another transaction to the same deposit address.

Which wallet are you using to make the transaction? I notice you are reusing the same address over and over for change (which is bad for your privacy, but that's a different matter). If you make a transaction using the change output from your currently unconfirmed transaction (0.00198082 BTC), you will effectively be performing a CPFP, and so your second transaction will need to pay more than the current required rate (about 50 sats/vbyte) for a fast confirmation since it is bumping the fee of the previous transaction too. If you use different inputs, then you will only need to pay 50 sat/vbyte.

Depending on which wallet you are using, you may not be able to specify which inputs to use, or it may not allow spending of unconfirmed inputs anyway.