got a tx got mined.... my friend and I extend a big THANK YOU nc50lc 
Topic: TX decode failed (Read 116 times)
different wallet WORKED got a tx got mined.... my friend and I extend a big THANK YOU nc50lc
got a tx got mined.... my friend and I extend a big THANK YOU nc50lc
Thanks for trying to help me figure it out what went wrong....
...using coinbin to make tx
> txn-mempool-conflict (code 18)
also tried switching Broadcast Network
> A valid signed transaction hexadecimal string is required. Please check if all inputs in the given transactions are still available to spend. See the "Is Tx Output Spent?" API call for reference.
my friend cant afford to loose $, but this is btc and it says it has not moved so that is comforting - eventually tx will age out of mempool right?
so adding your points to error code, will try importing key into another wallet and try to resend. If that does not work will try sending to original address with high fee and hopefully some nice miner will push the entire tx string through. will update - Thanks again
[\quote]But the input of the previous transaction isn't spent yet, did you used another input(s) for the recreated transaction?
Anyways, 1sat/vB is enough at the moment, it's 1-2 blocks away; but CPFP will definitely speed it up.
What's your client BTW? The previous transaction's input may be locked until you manually drop it from your wallet.
If the new transaction is using the previous' input, then it's not in the mempools yet.
Anyways, 1sat/vB is enough at the moment, it's 1-2 blocks away; but CPFP will definitely speed it up.
What's your client BTW? The previous transaction's input may be locked until you manually drop it from your wallet.
If the new transaction is using the previous' input, then it's not in the mempools yet.
...using coinbin to make tx
....[\quote] until you manually drop it from your wallet
so tried clearing all cache and temp files and recreating tx. but still mempool conflict error.> txn-mempool-conflict (code 18)
also tried switching Broadcast Network
> A valid signed transaction hexadecimal string is required. Please check if all inputs in the given transactions are still available to spend. See the "Is Tx Output Spent?" API call for reference.
my friend cant afford to loose $, but this is btc and it says it has not moved so that is comforting - eventually tx will age out of mempool right?
so adding your points to error code, will try importing key into another wallet and try to resend. If that does not work will try sending to original address with high fee and hopefully some nice miner will push the entire tx string through. will update - Thanks again
spot on that looks like the problem....recreated the transaction with higher fee
...but the transaction is now stuck in mempool with the sub 1 satoshi fee.
But the input of the previous transaction isn't spent yet, did you used another input(s) for the recreated transaction?...but the transaction is now stuck in mempool with the sub 1 satoshi fee.
Anyways, 1sat/vB is enough at the moment, it's 1-2 blocks away; but CPFP will definitely speed it up.
What's your client BTW? The previous transaction's input may be locked until you manually drop it from your wallet.
If the new transaction is using the previous' input, then it's not in the mempools yet.
But the transaction itself has an issue.
spot on that looks like the problem....recreated the transaction with higher fee
...but the transaction is now stuck in mempool with the sub 1 satoshi fee.
If i do child pays for parent push will that get the transaction through the mempool or do i have to wait until the mempool empties erroneous transactions....
You're getting "TX Decode Failed" probably because of the spaces,
did he sent it to you through bitcointalk's PM? because it will add some spaces in between some of the characters.
For that, you/he should enclose it between [code][/code] tags.
But the transaction itself has an issue.
Its fee rate is lower than the standard default of 1sat/vB, the total fee should be 168sat since the transaction's size is 168vB (it only has 139sat fee).
So, you wont be able to send it to most of the nodes (with default relay fee setting).
did he sent it to you through bitcointalk's PM? because it will add some spaces in between some of the characters.
For that, you/he should enclose it between [code][/code] tags.
But the transaction itself has an issue.
Its fee rate is lower than the standard default of 1sat/vB, the total fee should be 168sat since the transaction's size is 168vB (it only has 139sat fee).
So, you wont be able to send it to most of the nodes (with default relay fee setting).
Hi
Trying to help a friend send transaction. getting TX decode failed and the transaction never goes through but it creates a txid
txid: c2c70947428789d45c4436e7e50437f6a7fb173afd664d82a09052fa892a90c2
hex encoded bitcoin transaction:
01000000000101358a18691cd5b9c13d6159368b61f3cc97df6c3234aba3b2f539c507c91c27c00 1000000171600146315fc838d7e36e41b950f6274a481b34c2c4d0cffffffff02a86a0100000000 001976a91481037fba3ef8c13e0edaef4fb4ae86f966f9af7f88ac7d7022000000000017a914c92 0497e43dfbe9811b13c737d9791604d74b916870247304402205d0122cefa3458d80c5fbc7eaa65 2df86fa418630774b60b871add36dc9677c702200f26aec2bbd559105ea5a65b73fa3dd99cb8c2c 1a601c649846998bf5a2767ce0121021d61d3b9988a78fa59f55218cdbf089baf99f9cb6a20867a c9a21147b21ed1b700000000
Trying to help a friend send transaction. getting TX decode failed and the transaction never goes through but it creates a txid
txid: c2c70947428789d45c4436e7e50437f6a7fb173afd664d82a09052fa892a90c2
hex encoded bitcoin transaction:
01000000000101358a18691cd5b9c13d6159368b61f3cc97df6c3234aba3b2f539c507c91c27c00 1000000171600146315fc838d7e36e41b950f6274a481b34c2c4d0cffffffff02a86a0100000000 001976a91481037fba3ef8c13e0edaef4fb4ae86f966f9af7f88ac7d7022000000000017a914c92 0497e43dfbe9811b13c737d9791604d74b916870247304402205d0122cefa3458d80c5fbc7eaa65 2df86fa418630774b60b871add36dc9677c702200f26aec2bbd559105ea5a65b73fa3dd99cb8c2c 1a601c649846998bf5a2767ce0121021d61d3b9988a78fa59f55218cdbf089baf99f9cb6a20867a c9a21147b21ed1b700000000
Jump to: