Topic: Urgent - unconfirmed transaction in chain.so, and doesn't exist in blockchain (Read 1256 times)

Hi. I have noticed that HashFlare uses chain.so for payments, I have a pending payment from weeks ago, in there when entering my wallet I see a pending transaction (but that same transaction I do not see it in BlockChain.info). I also see a QR Code next to my pending payment, that QR code is Public or private ?. At the moment he is counting 15 transactions.

Some problem here : https://chain.so/tx/BTC/87f8bbbb215f70567baded1909432d3b0f95ceda98f6068dbcd715e9634a2804
Waiting since 4 days

Look, you have created a very complex transaction and it has been pointed out that at least one part has an error.

Do this. Send a smaller amount of coin - pick the amount so that you get maybe 30 inputs to it. Or 60, whatever. Get that done. Then do another one.

In other words, break the problem into pieces, and handle each piece one by one. At the end you may only be left with one problematic input.

The transaction still didn't drop...that's terrible. Over 72 hours have passed since it dropped for the first time, and situation is exactly the same...  

You should definitely stop using block.io until they can figure out how to properly create transactions.  In this case...

Your transaction f89b79d5222a2016d0d2e0059d8834a61da817fd9ad31b3d58e0770cba4ddd87 is trying to spend bitcoins from 14 unconfirmed transactions:

• 50f297c4a5b21e388daee36dc28bd60a19982f0dfbe3cdd71815cc532c033c27 (transaction fee only 1 sat/B)
• 787a5be43866e5eaa156aeb81b908d98eef88c3431515bd59779ebbde22934c1 (transaction fee only 1 sat/B)
• 846ee142c8a67aec0d85f4f79b6d77cc3b0544b9749a51c72dffba67a6da97bb (transaction fee only 1 sat/B)
• f5e05b10bae4e43ca92c64c3fc5221b27611d3003647ca096a67ed00c83b56fe (transaction fee only 1 sat/B)
• 6456fbfa94a9e8b59d837fa8ab7aa71ad6613f9a51829affc6ce3a48b291ca9b (transaction fee only 2 sat/B)
• 076654918d9adba729d3dcaf7d030ffb9d934b3b51b773d25cdaa1cce540c0bd (transaction fee only 2 sat/B)
• 5183b6349fed6fb86c93c8fe2c7bb6bff5bfe996c5d3d5688107b0e712609002 (transaction fee only 2 sat/B)
• 9eb2de76ddda2a0f630e68ea359425a57a73398408f9c1ee94ca560085a55c51 (transaction fee only 2 sat/B)
• 9faa6b20986f8c32865a3a68192c5955f4037fa002df471b651ad601aa2805a2 (transaction fee only 2 sat/B)
• 39c7524f2237b0cab663077aa98a13e99dba95c241efb9563d9afba674e9140d (transaction fee only 2 sat/B)
• 6cd5de85e14dd1f46ff15e4ede649f44d9b18b7be68ea94f509c4984cac5c429 (transaction fee only 2 sat/B)
• 30132040ebe219bad8c5846fd33c6b6de9ff2e9822f936aecaf9072515207faf (transaction fee only 2 sat/B)
• 4fefbb6ab9b6b321aa7ce5c4df2fae74e14f4b794cebe896cbce3471ac836e86 (transaction fee only 2 sat/B)
• 1d7371da636f215fbb7d5df8eca12aed98a930647885b190ddcfe9db67f217b6 (transaction fee only 2 sat/B)

Your transaction will not be able to confirm until all 14 of those earlier transactions confirm.

Unfortunately, all of these pending transaction paid an extremely low transaction fee so it is unlikely that any of them will confirm soon.

Additionally, two of those earlier transactions:

• 787a5be43866e5eaa156aeb81b908d98eef88c3431515bd59779ebbde22934c1
• 846ee142c8a67aec0d85f4f79b6d77cc3b0544b9749a51c72dffba67a6da97bb

are both trying to spend bitcoins from even earlier unconfirmed transactions:

• 68c0414bc7b8cf88cfd7d56c12e5c05bfc33bd6e534754ce5aca884a31c0eb51 (transaction fee only 1 sat/B)
• 709f12127cf4ae81f99ff6f591d9f1e53c363a67547e3bc22c6175cdb40d4bf5 (transaction fee only 1 sat/B)

The transactions you are waiting on will not be able to confirm until these two even earlier transactions confirm.

Those two transactions ALSO paid an extremely low transaction fee so it is unlikely that either of them will confirm soon.

You won't be able to fix this unless you can get access to all the private keys AND the redeem script for:
3CdYdQcc79QywRbZsAToKJx3AC83GGr1Ke

If you have access to all the private keys, AND the redeem script for that address, then it should be possible to create a replacement transaction that invalidates:
68c0414bc7b8cf88cfd7d56c12e5c05bfc33bd6e534754ce5aca884a31c0eb51

If that replacement transaction pays a high enough fee to confirm quickly, then the following transactions will become invalid and will disappear from the network:

• 68c0414bc7b8cf88cfd7d56c12e5c05bfc33bd6e534754ce5aca884a31c0eb51
• 787a5be43866e5eaa156aeb81b908d98eef88c3431515bd59779ebbde22934c1
• f89b79d5222a2016d0d2e0059d8834a61da817fd9ad31b3d58e0770cba4ddd87

This would effectively "cancel" your transaction, but would not free up all the pending funds in the other 13 unconfirmed transactions.

Any of those pending transactions that were sent by you using private keys and redeem scripts that you can get access to can also be effectively "cancelled" by including their funds in your replacement transaction.  Any of those pending transactions that were NOT sent by you or used private keys or redeem scripts that you can NOT get access to will require assistance from the person (or persons) in control of the private keys and redeem scripts.

Fees are extremely high now. Very bad time for the Bitcoin network, which is too overloaded atm. What happened to SegWit? 

Same here, waiting since yesterday, the sender is a third party.
The transaction only shows up on chain.so, nowhere else, and no BTC was received.
Let's see where's this heading

No solutions yet! 

I have the same problem like you.
Did you found any solutions?

My situation worse than you because sender is not me.

Looking forward to assistance. 

Ok, but it's 4 days already. Only yesterday early morning I had a chance to send another transaction with a high priority from my Block.io wallet, but I missed that chance as I didn't expect the transaction to rebroadcast again. Anyway, so how can I access my Block.io wallet funds using the Private Keys? I still didn't find a way. There must be a solution to this and I hope that someone can help me. And by the way, there is still no answer from Block.io support.

Ohhhhh... it's a SegWit address... OK, all bets are off. I honestly have no idea what you need to do at this point... but that probably explains the "witness program does not match script hash" error...

As far as I can tell, I *think* that there are inputs used in your original transaction that are no longer available (ie. they've been spent in different transactions)... so I don't think your original transaction will ever confirm. It would appear that someone (your wallet? block.io? the receiving wallet? some other 3rd party?) is trying to rebroadcast that original transaction.

Give it a day or so... and it should all settle down and the transaction should be completely dropped from the mempool and your wallet should show you the coins etc.

And here is the information that I get from Block.io when retrieving private keys for address 3CdYdQcc79QywRbZsAToKJx3AC83GGr1Ke :

* Address: 3CdYdQcc79QywRbZsAToKJx3AC83GGr1Ke

* Address Type: P2WSH-over-P2SH

* Required Signatures: 2

* Redeem Script: 2 *** 2 OP_CHECKMULTISIG

* Redeem Script Hex: ***

* Public Keys: ["***", "***"]

* Private Keys: ["***", "***"]

I tried to open MultiSig wallet in Electrum but failed, because I don't have xpubs or xprvs. I only have the above information from Block.io and from coinb.in.

I don't understand.

In coinb.in site in "Verify" section, I entered the redeem script of address 3CdYdQcc79QywRbZsAToKJx3AC83GGr1Ke  and got the following information:

Multi Signature Address, Required Signatures (2), and Signatures Required from (2 addresses and 2 public keys).

What to do next? I am stuck. Please help me.

That's because block.io is using P2SH (Pay to Script Hash) addresses... possibly a MultiSig (hence the multiple private keys).  So, you'd need to create a MultiSig wallet using the two private keys they gave you... not even sure that is possible to create a single address MultiSig with Electrum, or if you have to use xpubs/xprv's... fairly sure it ONLY accepts xpubs and xprvs

You'd probably need to use something like Coinb.in to recreate the MultiSig, create your raw transaction, sign it and broadcast from there. Obviously, I would recommend downloading a copy of Coinb.in and running it on an offline machine to reduce exposure of your private keys


Also, it would appear that there is a reason the transaction was pretty much rejected by the entire network:
It seems (at least) one of the inputs is from a "bad transaction"... I tried to repush the "53fdc" transaction via BlockCypher, and it says:


Something seriously screwed up with all of that...

Seems like the Private Keys feature of Block.io isn't working properly...

I will ask Block.io to manually drop that transaction from their mempool then.

I imported to my Electrum wallet my 2 Private Keys of the Bitcoin address (3CdYdQcc79QywRbZsAToKJx3AC83GGr1Ke) from which the transaction was sent, but it gave me 2 empty addresses with zero transactions....that's so strange.

Not sure how it works with block.io, but you already mentioned you could export your private keys, well, do that.

Simply download electrum from here, https://electrum.org/#download

And here's if you want to simply make a new wallet, which is what you want to do in your case, http://docs.electrum.org/en/latest/faq.html#can-i-sweep-private-keys-from-other-bitcoin-clients

Or possible add it to an existing wallet, assuming you already have an electrum wallet. http://docs.electrum.org/en/latest/faq.html#can-i-import-private-keys-from-other-bitcoin-clients

Also, this won't lower the amount of fees you'd need to sent, but it does probably make it easier to broadcast a transaction.


Aha, didn't see that, only checked the blockchain.info links, and they were all dead. Over 300+ inputs probably isn't that good for your average fee^

Indeed, I didn't check the fee. If it's too small ViaBTC won't accept it. But afaik people accelerate on other pools too.
And I guess that the pools have their own mempool and some may still have the tx.
It's just an idea, it's your decision what steps you do next.

Of course. If they would do it in the first place.
Yes. Since your fees are way too low, its very possible that majority of the network has not seen your transaction yet. With that, the servers in Electrum would also probably have not seen your transaction yet. Hence, the address would appear as if the transaction that you made has never been made before. To do that, create a standard wallet in Electrum and select Use public or Private keys and paste your private key in.
https://chain.so/tx/BTC/f89b79d5222a2016d0d2e0059d8834a61da817fd9ad31b3d58e0770cba4ddd87
For transactions with fees of 0.0001BTC/KB and above.