Full RBF is a setting for nodes. If a node has enabled full RBF, it treats all transactions as RBF-enabled and accept the replacement transaction, even if the original transaction has not flagged as RBF.
If you have a non-RBF transaction and you want to replace that with a new transaction, you should broadcast your transaction from a node that has enabled full RBF.


Bitaccelerate don't accelerate your transaction at all. They only rebroadcast your transaction and that's different from accelerating.

Check the following location and see if you can find your wallet file. If you have the wallet file and know the password (if it's encrypted), you can have access to you fund even without knowing the seed phrase.

Users\YourUserName\AppData\Roaming\Electrum (or %APPDATA%\Electrum)

For more information, visit this: Where is the Electrum datadir located?

The purging fee rate for any node with default mempool size is now around 23 sat/vbyte and almost all nodes should accept and relay transactions paying 30 sat/vbyte.

If you make a transaction paying 30 sat/vbyte now, it would be around 50 vMB from the tip of mempools.
If you pay 1 sat/vbyte more and use the fee rate of 31 sat/vbyte, your transaction would be only 3 vMB from the tip of mempools.

There are many block explorers that can be used for checking transactions and balance of any address you want. Note that all bitcoin transactions are public.

Here are some good block explorers.

• mempool.space
• blockchair.com
• blockcypher.com
• blockstream.info

You can spend all 3 BTC in one transaction and you will have to provide three different signatures in your transaction.

Every time you create a bitcoin transaction, you create output(s) and you define a locking script for each of the outputs.
Anyone who wants to spend any of the outputs in a new transaction must provide an unlocking script which usually requires a signature.

Take note that even if you had made the three transactions to the same bitcoin address, you would still have to provide three different unlocking scripts with three different signatures for spending them.

Here are the addresses that can be derived from your private key. They are all empty.

• Uncompressed legacy: 1KLT97kA8Jw7hSzFnVQBoHEgTH7LbrFZBM
• Compressed legacy: 1DGdSzSj8anhcmsGcfRaYmV63U29TwFPGH
• Nested segwit: 3FVDAHLkNhFxA459tt6E8j7SXWV8mfTekK
• Native segwit: bc1qs6tze9e6shjq9hxtx3ye2wqyt7hkngrd38kksh

Did you purchase the private keys? If so, you got scammed.

This is my question, too.

I doubt OP has created the private keys by himself.
As you said, it's not common to have a 64 character private key and I don't think there's any wallet displaying private keys in such format.

Maybe, OP has purchased some worthless private keys and someone has scammed him.


You are right, but we don't know where OP got the $10 from.
There's chance that's a private key of an old address that received $10 worth of bitcoin in the past and now it costs more.

I received a message from OP.

He doesn't know the bitcoin address at all.
He said he has multiple hex private keys. One of them is for an address with only $10 worth of bitcoin and he asked me if I can check it.

I warned him about messages not being encrypted and the risk involved in sending a private key via pm.
He said he doesn't mind losing the $10 and insisted on sending me the hex private key.


Trendy555, I just sent you my protonmail address.
You can create a protonmail account (if you don't have) and send me the private key. In this way, your message would be more secure.


I can't guarantee the security of your fund and note that with sending your private key online, you are accepting the risk of losing your money (if there's any, of course).

The error message means that there is no fund at the address derived from the private key you are sweeping.

Do you know your bitcoin address or all you have is the hex private key?
Maybe, that the fund is at the segwit address.

If the fund is at the native segwit address, you should add "p2wpkh:" before your (compressed) private key and if the fund as the nested segwit address, you should add "p2wpkh-p2sh:" before your (compressed) private key.

Native segwit addresses start with bc1 and nested segwit addresses start with 3.

Their push transaction service can surely act as a transaction accelerator, but that's not only a transaction accelerator.


I don't know whether their push transaction service is free or not.
They require users to enter a referral code because they don't want everyone to be able to use that service and I think that's because they allow submitting non-standard transactions.


Here are the differences.

• In their transaction accelerator, you should submit your transaction ID and therefore, your transaction should have been broadcasted before using other tools and they should have your transaction in their mempool. In their push transaction service, you should submit the raw transaction in hex and you send your transaction directly to F2Pool.
  
  
• In their transaction accelerator, you can't submit a non-standard transaction, but in their push transaction service, you can submit even a non-standard transaction.

There's a big difference between F2Pool push transaction service and other tools that can be used for broadcasting transactions.
Anyone who has a referral code can send a non-standard transaction directly to F2Pool, so that they include it in the blockchain.

If a node displays your transaction status as unconfirmed, it means that the node has your transaction in its mempool.

Whenever you use electrum, you connect to server a to get data from. Each server runs a node and each node has its own mempool and can have its own setting.

If the server you are connected to has the transaction in its mempool, it would display your transaction status as unconfirmed.
If the server you are connected to doesn't have your transaction in its mempool, that doesn't have any information about your transaction and wouldn't display that at all.

Take note that with changing the server, you don't change anything with the transaction and you only decide to get data from a different node.

If the fee you use for the new transaction is high enough, those nodes that have the old transaction will replace that with the new transaction.
If the fee you use for the new transaction isn't high enough, those nodes that have the old transaction will reject the new transaction and will keep the old one.

Once one of the transactions gets confirmed, the other one would be invalidated and wouldn't have any chance to be confirmed.


By the way, transactions are not confirmed by the nodes. They are confirmed by the miners.

Being local means that the transaction exists in the wallet file, but the server you are connected to doesn't have it in its mempool.


With removing the transaction, you would remove your transaction from the wallet file.
Take note that any node that has your transaction in its mempool will still have your transaction, even if you remove it. Once you connect to a server that has your transaction in its mempool, your transaction will appear again.

As mentioned above by o_e_l_e_o, you can remove your local transaction, so that you can make a new transaction.
If you don't want to make a new transaction after removing the local transaction, you wouldn't change anything just with removing the local transaction.

The option to enable/disable RBF has been removed since the version 4.4.0 of electrum and all transactions are automatically flagged as RBF.


OP posted the transaction status and according to that, the transaction has been broadcasted by the server.
Nodes can have their own setting and it's not that they all have the same purging fee rate.

Of course, many other nodes have probably rejected OP's transaction and it's possible that the transaction status changes to local once OP is connected to a different server.

To add to Charles-Tim's post:

Whether the unconfirmed transaction is shown in electrum or not depends on which electrum server you are connected to. There are nodes that still have the transaction in their mempool and it's possible that electrum show the unconfirmed transaction.

If the unconfirmed transaction is not displayed in electrum, you can easily make a new transaction.
If the unconfirmed transaction is displayed in electrum, you should try connecting to different servers, until you find a one that doesn't have your transaction in its mempool. After that you will be able to remove the transaction from the wallet locally and make a new transaction.

You don't need to have a referral code for using their transaction accelerator and they allow everyone to use that.
Referral code is required, if you want to use their Push TX service. For pushing a transaction, you should submit the raw transaction in hex and that's a different service.

The number displayed by electrum as fee rate is in sat/vbyte, although electrum is still showing that in sat/byte.
The size displayed by electrum is also in vbytes, not bytes.

All bitcoin explorers I know display the virtual size of the transactions or their weight. Even some explorers show both of them.


Here is a transaction on blockchair.com.



The fee rate is 247 sat/vbyte and the weight is 449.
The virtual size of the transaction is 449/4 = 112 vbytes.

I don't get this.
What do you mean by the other chart and where did you get the 40 sat/byte?

Miners prioritize transactions based on the fee paid for each virtual byte of data and therefore what matters is the fee rate in sat/vbyte.


By doing so, you calculate the fee rate in sat/byte.
As I said what matters is the fee rate in sat/vbyte. For calculating that, you should divide the fee by virtual size of the transaction.
It may worth mentioning that virtual size of a transaction (in vbytes) is equal to number of weight units divided by 4.

Take note that when you recover the wallet, all the addresses are generated at the same order as the original wallet and people usually don't need to increase the gap limit.
Also note that the gap limit of 20 means that electrum stops generating new addresses once it reaches 20 consecutive unused addresses.
For example, if you have used the 20th address, electrum will generate at least 40 addresses and check their transactions history, even if you haven't used the first 19 addresses and you haven't increased the gap limit.

If you go to receive tab, click on "Create request" again and again until it generates an address beyond the gap limit for you, electrum even displays a message warning you about the address being beyond the default gap limit and also highlight them in red in "Addresses" tab.

Therefore, you should know if you have funded an address beyond the gap limit and if you have done so, you can easily increase the gap limit using the following command after restoring the wallet from seed phrase.

This command will increase the gap limit to 50. You can change the 50 to any number you want.

You can also generate more addresses without increasing the gap limit using the commands posted above by o_e_l_e_o.



You wouldn't have any issues with the derivation path if the seed phrase has been generated by electrum itself.
Even if the seed phrase is BIP39, most wallets use common derivation paths and you still don't need to save the derivation path and as mentioned by o_e_l_e_o above it can be easily detected.

If you have generated a wallet using a non-standard derivation path, you must know it when restoring the wallet from the seed phrase.


You generated the wallet and it's you that should know whether a passphrase was used or not.


Again, you are the one who must know whether the seed phrase has been generated by electrum itself or not.
And even if you don't remember that, (as mentioned above by o_e_l_e_o) electrum would detect the seed phrase type if it has been generated by itself, once you enter that.