Btc transaction not verified after 3 days

[Joopii]

I sent a Bitcoin transaction of 8.5 btc 3 days and 8 hours ago with a fee of 0.0001 btc and it still does not have a single confirmation. I tested sending a few smaller transactions since then and they got confirmed shortly after.
Is it normal to take so long and is there any way to speed up the process?

[repas-sventa]

I sent a Bitcoin transaction of 8.5 btc 3 days and 8 hours ago with a fee of 0.0001 btc and it still does not have a single confirmation. I tested sending a few smaller transactions since then and they got confirmed shortly after.
Is it normal to take so long and is there any way to speed up the process?

Intresting. Your fee is ok. Cant wait to see what experts going to answer

[BADecker]

Have you checked to see if the transaction went through?

https://blockchain.info/

[Joopii]

Have you checked to see if the transaction went through?

https://blockchain.info/

"Sorry we could not find any blocks or transactions matching this hash".
However I can still see the transaction on my wallet and the Bitcoins were removed from my wallet.

[shorena]

Have you checked to see if the transaction went through?

https://blockchain.info/

"Sorry we could not find any blocks or transactions matching this hash".
However I can still see the transaction on my wallet and the Bitcoins were removed from my wallet.

Which wallet software / service do you use? Its possible that the transaction was not properly send to the network or is forgotten by now.

[Joopii]

Have you checked to see if the transaction went through?

https://blockchain.info/

"Sorry we could not find any blocks or transactions matching this hash".
However I can still see the transaction on my wallet and the Bitcoins were removed from my wallet.

Which wallet software / service do you use? Its possible that the transaction was not properly send to the network or is forgotten by now.

I'm using the wallet from Bitcoin.org

[repas-sventa]

Try using multisignature copay wallet

[shorena]

Have you checked to see if the transaction went through?

https://blockchain.info/

"Sorry we could not find any blocks or transactions matching this hash".
However I can still see the transaction on my wallet and the Bitcoins were removed from my wallet.

Which wallet software / service do you use? Its possible that the transaction was not properly send to the network or is forgotten by now.

I'm using the wallet from Bitcoin.org

Bitcoin core? They link many popular wallets -> https://bitcoin.org/en/choose-your-wallet

Assuming its core you can resend the transaction as is via the console (Help -> Debug Window -> console) or remove it from your wallet (see below)

First you need the transaction in its raw form. Which you can get by just asking the wallet with:
getrawtransaction TX-ID-here

It will return a long string to rebroadcast the TX write:
sendrawtransaction long-string-here

it should confirm with the TX-ID from step one.

To remove the unconfirmed TX from your wallet and create a new one via the GUI as usual:

#1 close bitcoin core
#2 start it with -zapwallettxes, e.g. for windows you open run (Win + R) and enter the following before you confirm with ok.

Code:

c:\Program Files\Bitcoin\bitcoin-qt.exe -zapwallettxes

Try using multisignature copay wallet

If your car is broken, using a bike will not fix the car

[Joopii]

Have you checked to see if the transaction went through?

https://blockchain.info/

"Sorry we could not find any blocks or transactions matching this hash".
However I can still see the transaction on my wallet and the Bitcoins were removed from my wallet.

Which wallet software / service do you use? Its possible that the transaction was not properly send to the network or is forgotten by now.

I'm using the wallet from Bitcoin.org

Bitcoin core? They link many popular wallets -> https://bitcoin.org/en/choose-your-wallet

Assuming its core you can resend the transaction as is via the console (Help -> Debug Window -> console) or remove it from your wallet (see below)

First you need the transaction in its raw form. Which you can get by just asking the wallet with:
getrawtransaction TX-ID-here

It will return a long string to rebroadcast the TX write:
sendrawtransaction long-string-here

it should confirm with the TX-ID from step one.

To remove the unconfirmed TX from your wallet and create a new one via the GUI as usual:

#1 close bitcoin core
#2 start it with -zapwallettxes, e.g. for windows you open run (Win + R) and enter the following before you confirm with ok.

Code:

c:\Program Files\Bitcoin\bitcoin-qt.exe -zapwallettxes

Try using multisignature copay wallet

If your car is broken, using a bike will not fix the car

Sorry for the late reply, it took a couple days when I attempted to reinstall the blocks to my wallet, which did not help and my payment still hasn't been confirmed.
I just tested resending the transaction as you suggested but when I enter the "sendrawtransaction", it returns "TX rejected (code -22)".

Also opening the wallet with zapwallettxes did not change anything.

[FrostStick]

Can you tell us the transaction ID involved?

[Joopii]

Can you tell us the transaction ID involved?

c3f20d280175dddfe7e682791698717990645092bb58924928c24698a2aeb51c-000

[achow101]

Sorry for the late reply, it took a couple days when I attempted to reinstall the blocks to my wallet, which did not help and my payment still hasn't been confirmed.
I just tested resending the transaction as you suggested but when I enter the "sendrawtransaction", it returns "TX rejected (code -22)".

Also opening the wallet with zapwallettxes did not change anything.

Can you post the output of getrawtransaction?

[FrostStick]

Can you tell us the transaction ID involved?

c3f20d280175dddfe7e682791698717990645092bb58924928c24698a2aeb51c-000

Hmm very weird. Let's hang around and see what happens. Maybe rebroadcast the transaction?

[Joopii]

Can you tell us the transaction ID involved?

c3f20d280175dddfe7e682791698717990645092bb58924928c24698a2aeb51c-000

Maybe rebroadcast the transaction?

How would I do that?

[achow101]

Can you tell us the transaction ID involved?

c3f20d280175dddfe7e682791698717990645092bb58924928c24698a2aeb51c-000

Maybe rebroadcast the transaction?

How would I do that?

You have to do what shorena said, but it doesn't work for you because of an error

Error code -22 means that there was an error in validating the transaction. Please post the output of your getrawtransaction command so that other people can try broadcasting for you as well. You can also try broadcasting it on various pushtx interfaces like https://blockchain.info/pushtx

[FrostStick]

Weird because you've paid the full recommended miners fees..... Most of these cases are from people trying to save that 2 cents and ends up waiting ages for their bitcoins to arrive.

[Joopii]

Can you tell us the transaction ID involved?

c3f20d280175dddfe7e682791698717990645092bb58924928c24698a2aeb51c-000

Maybe rebroadcast the transaction?

How would I do that?

You have to do what shorena said, but it doesn't work for you because of an error

Error code -22 means that there was an error in validating the transaction. Please post the output of your getrawtransaction command so that other people can try broadcasting for you as well. You can also try broadcasting it on various pushtx interfaces like https://blockchain.info/pushtx

The raw transaction is here:
010000000375543fbecc1e69cb6dfb38c8c1a7847088a125bcced7a91c1cf335c887d6ba2d00000 0006a4730440220219fe21d2d947ef6fc7802406269b47e7d62b6bc069cc4bd43651d97ec36e149 02207f25b17cb1b1bf21f457c07d9f68da84abe28a5a4ae111d8fb523ef4c148f859012102cdf6c b06664b647bc8935bdf4b052e10ad6b758ac2888d5db6053ad8ba05e68cffffffff132e3f3dcda1 bee514097eace3fd89d66a0e6fd75ec7086fab573d5f2382e327010000006c493046022100b67e8 4f2d24cc69e5a5ff755ba6d06525f3c9e4b260446827acfd9a74ca77d7e022100dbc74f91093fed d55a3cb00062134326be655430c448efc9afb30a813abb5493012103e51858147fd99c7a53cbcbb 61dc7f28bd80c841be346230f85e27829611e7d8dffffffff04bc32c5b42857af03af6c81d26465 ccef379a45e678f9c34bd8d492e512565a010000006b48304502200b8a06c99345ee30a476ee369 a2a8762765e9d5abc4daef35649c884671d2988022100aa42882c36a0cfe62272fb3f3715c986ea da7344b309267e6f8471f2ac0e41cc0121039fc050d66cea72b6f8c882df05f7b51afdab9b1817f cf8b74f74ce703a0ad749ffffffff0280f8a932000000001976a9144fbe0d312290f5fcdbb78864 52808074dcec230e88ac343a9001000000001976a91468307edb518c000a17b013e9736f969a1c1 a945c88ac00000000

[achow101]

Can you tell us the transaction ID involved?

c3f20d280175dddfe7e682791698717990645092bb58924928c24698a2aeb51c-000

Maybe rebroadcast the transaction?

How would I do that?

You have to do what shorena said, but it doesn't work for you because of an error

Error code -22 means that there was an error in validating the transaction. Please post the output of your getrawtransaction command so that other people can try broadcasting for you as well. You can also try broadcasting it on various pushtx interfaces like https://blockchain.info/pushtx

The raw transaction is here:
010000000375543fbecc1e69cb6dfb38c8c1a7847088a125bcced7a91c1cf335c887d6ba2d00000 0006a4730440220219fe21d2d947ef6fc7802406269b47e7d62b6bc069cc4bd43651d97ec36e149 02207f25b17cb1b1bf21f457c07d9f68da84abe28a5a4ae111d8fb523ef4c148f859012102cdf6c b06664b647bc8935bdf4b052e10ad6b758ac2888d5db6053ad8ba05e68cffffffff132e3f3dcda1 bee514097eace3fd89d66a0e6fd75ec7086fab573d5f2382e327010000006c493046022100b67e8 4f2d24cc69e5a5ff755ba6d06525f3c9e4b260446827acfd9a74ca77d7e022100dbc74f91093fed d55a3cb00062134326be655430c448efc9afb30a813abb5493012103e51858147fd99c7a53cbcbb 61dc7f28bd80c841be346230f85e27829611e7d8dffffffff04bc32c5b42857af03af6c81d26465 ccef379a45e678f9c34bd8d492e512565a010000006b48304502200b8a06c99345ee30a476ee369 a2a8762765e9d5abc4daef35649c884671d2988022100aa42882c36a0cfe62272fb3f3715c986ea da7344b309267e6f8471f2ac0e41cc0121039fc050d66cea72b6f8c882df05f7b51afdab9b1817f cf8b74f74ce703a0ad749ffffffff0280f8a932000000001976a9144fbe0d312290f5fcdbb78864 52808074dcec230e88ac343a9001000000001976a91468307edb518c000a17b013e9736f969a1c1 a945c88ac00000000

The problem is that the input transactions that transaction references don't exist. Those transactions referenced by this one were malleated, they had High S signatures and someone malleated their transaction to use Low S signatures. The original transactions with the High S were then discarded by most of the network so those remained unconfirmed while the other malleated transaction was the one that was confirmed. You will need to create a new transaction that uses the inputs that were confirmed. Try using zapwallettxes then sending the transaction again.

[Joopii]

Can you tell us the transaction ID involved?

c3f20d280175dddfe7e682791698717990645092bb58924928c24698a2aeb51c-000

Maybe rebroadcast the transaction?

How would I do that?

You have to do what shorena said, but it doesn't work for you because of an error

Error code -22 means that there was an error in validating the transaction. Please post the output of your getrawtransaction command so that other people can try broadcasting for you as well. You can also try broadcasting it on various pushtx interfaces like https://blockchain.info/pushtx

The raw transaction is here:
010000000375543fbecc1e69cb6dfb38c8c1a7847088a125bcced7a91c1cf335c887d6ba2d00000 0006a4730440220219fe21d2d947ef6fc7802406269b47e7d62b6bc069cc4bd43651d97ec36e149 02207f25b17cb1b1bf21f457c07d9f68da84abe28a5a4ae111d8fb523ef4c148f859012102cdf6c b06664b647bc8935bdf4b052e10ad6b758ac2888d5db6053ad8ba05e68cffffffff132e3f3dcda1 bee514097eace3fd89d66a0e6fd75ec7086fab573d5f2382e327010000006c493046022100b67e8 4f2d24cc69e5a5ff755ba6d06525f3c9e4b260446827acfd9a74ca77d7e022100dbc74f91093fed d55a3cb00062134326be655430c448efc9afb30a813abb5493012103e51858147fd99c7a53cbcbb 61dc7f28bd80c841be346230f85e27829611e7d8dffffffff04bc32c5b42857af03af6c81d26465 ccef379a45e678f9c34bd8d492e512565a010000006b48304502200b8a06c99345ee30a476ee369 a2a8762765e9d5abc4daef35649c884671d2988022100aa42882c36a0cfe62272fb3f3715c986ea da7344b309267e6f8471f2ac0e41cc0121039fc050d66cea72b6f8c882df05f7b51afdab9b1817f cf8b74f74ce703a0ad749ffffffff0280f8a932000000001976a9144fbe0d312290f5fcdbb78864 52808074dcec230e88ac343a9001000000001976a91468307edb518c000a17b013e9736f969a1c1 a945c88ac00000000

The problem is that the input transactions that transaction references don't exist. Those transactions referenced by this one were malleated, they had High S signatures and someone malleated their transaction to use Low S signatures. The original transactions with the High S were then discarded by most of the network so those remained unconfirmed while the other malleated transaction was the one that was confirmed. You will need to create a new transaction that uses the inputs that were confirmed. Try using zapwallettxes then sending the transaction again.

I tried zapwallettxes but nothing changed. Is there anything else I can do?

[achow101]

I tried zapwallettxes but nothing changed. Is there anything else I can do?

Was the transaction in question removed from your wallet? It should have been removed since it is still unconfirmed.

Have you tried sending another transaction after you did zapwallettxes?