Author

Topic: Bitcoin Core v5.7.1 Transaction unconfirmed 3 days, TX rebroadcast gives errors. (Read 163 times)

legendary
Activity: 4214
Merit: 1313
Just in case someone looks at this later to avoid confusion, the current version of Bitcoin Core is 0.15.1.  There is no 5.7.1. He is perhaps talking about the qt version.
hero member
Activity: 1232
Merit: 738
Mixing reinvented for your privacy | chipmixer.com
I was expecting hex rawtx Cheesy but anyway vh has accelerated it successfully
that was probably the fastest stuck tx problem solved so far,
I noticed mempool size dropped down a bit in the last 12 hours and min tx fee likewise
hero member
Activity: 602
Merit: 500
I nearly pooped myself when I saw it starting top confirm in Bitcoin core.  I was confused then I remembered to check here and I saw that you did.  Thank you so much for taking the time to do this.
vh
hero member
Activity: 699
Merit: 666
re-broadcasted:
https://live.blockcypher.com/btc/pushtx/

and set into viabtc.
https://pool.viabtc.com/tools/txaccelerator/

3d6d03427bcca999cb78e3502a81cec8ea13c907ac3c2530cbd7fac193ee3eba
response: Acceleration succeeded

it should clear on their next block.



edit:
Included In ViaBTC Block
499555 ( 2017-12-16 06:42:22 + 5,954 minutes )
hero member
Activity: 602
Merit: 500
Raw Tx as requested.

2
inputs   
0   
sequence   4294967294
witness   ""
prev_out   
spent   true
tx_index   311119975
type   0
addr   "13NFY7oK7oBFAQHBMx2fYbSTwLAVerYNpV"
value   3077110
n   2
script   "76a91419f51f08c14ce0b8c6c3a6d5c4b1a8c1d8e717b188ac"
script   "47304402200d8c4bf1eee8b06ee90e2056f6e74be596630a85181ca168ead5e80b9a4227b402200 cc18e367d5e8ae0496af256785ac53921e4a7c768ae0d0b3324850a5bd6db2501210222b33bd7b5 83d6011aad1ec92837f9dec9c0c99385accedf33dec6a2547d4460"
1   
sequence   4294967294
witness   ""
prev_out   
spent   true
tx_index   311124504
type   0
addr   "1xMD8Yt2pU3AjndMTc8DwAoEo4uhmYsKX"
value   2000555
n   13
script   "76a9140a77bf654efd1fccde9fcf5bc071cdc7e1eb4c5688ac"
script   "483045022100b4b83a66dd0edda350292a054491af9550f0073e326df8609421dd3bc33e75d1022 03e937640a4eb6aac8a603ada9a6044c522131a0ffeadf845fb75a283f8a6532a01210212d5cf45 717aea5bd4818964d3219ae6493c605b5f15384bb039012f543e81df"
2   
sequence   4294967294
witness   ""
prev_out   
spent   true
tx_index   311113905
type   0
addr   "1MHuf3Smp8fe7EijXEDnybFSMCZP2PQdjr"
value   2202144
n   34
script   "76a914de95204137b1323aa4bb590cc0da0287839257ba88ac"
script   "47304402203b9d2dbaef613834ee1b910a04655c5722751956b4f5c6023f516675ec3abc3002201 e050a018b45d6b99de2ef632e05ff8c39f51fc58f5770cd3b3afca17ee1d52d01210367900d7e70 d30907d3dc4e222b0bb04828d0f38fdeceb45af4bf53cfb99cb7a5"
3   
sequence   4294967294
witness   ""
prev_out   
spent   true
tx_index   311194627
type   0
addr   "1M4Sm6ehf8wCRuRZV2LNWcUT5n8reF4yLE"
value   2719755
n   16
script   "76a914dc094465b05769acee069393df16c86cfb8a059b88ac"
script   "473044022003d31c3995064f6c90d45cf18012bcd9bcaf66b877c868b9828008197ee5799402202 01948e7da3f8a74ae2be4203f365b648039bd4e41ecb4d98754470c1f219d1f012102ec6b4fb3ef b58e6a5926b4cb96b1da47e1a8f6edd7c3d67d398f688f4eb4940d"
weight   2532
relayed_by   "0.0.0.0"
out   
0   
spent   false
tx_index   311203421
type   0
addr   "1QEjKWh1pAKRAaY5QWjo3mDDXgnVKNDQeJ"
value   9948684
n   0
script   "76a914fee3a0759eceefa997bc6de6243db19abd077bbc88ac"
lock_time   498741
size   633
double_spend   false
time   1513049330
tx_index   311203421
vin_sz   4
hash   "3d6d03427bcca999cb78e3502a81cec8ea13c907ac3c2530cbd7fac193ee3eba"
vout_sz   1
hero member
Activity: 1232
Merit: 738
Mixing reinvented for your privacy | chipmixer.com
Forgot to add. 

I sent a  2nd Tx that did work as a test, after that I did the zapwallettxes command while reopening Bitcoin Core, and the original 0.1 show up there and the old TX that gave the parse error is gone,

but I cannot send that BTC.  Any time I try the Tx does not show up on blockchain.info.  Have tried this twice now.

So still do not have access to the 0.1 BTC

txid 3d6d03427bcca999cb78e3502a81cec8ea13c907ac3c2530cbd7fac193ee3eba still exist in bc.info mempool
pushing new tx with the same inputs will be rejected by bc.info
but "Parse: Error Parsing Transaction" you get from bc.info might be because your version Bitcoin Core v5.7.1 (is this correct version?)
paste here your rawtx that gets error parsing on bc.info, one of us might be able to figure out why
hero member
Activity: 602
Merit: 500
Forgot to add. 

I sent a  2nd Tx that did work as a test, after that I did the zapwallettxes command while reopening Bitcoin Core, and the original 0.1 show up there and the old TX that gave the parse error is gone,

but I cannot send that BTC.  Any time I try the Tx does not show up on blockchain.info.  Have tried this twice now.

So still do not have access to the 0.1 BTC
hero member
Activity: 602
Merit: 500
TX: 3d6d03427bcca999cb78e3502a81cec8ea13c907ac3c2530cbd7fac193ee3eba

Bitcoin Core v5.7.1
Windows 7 64

Amount is about 0.1 BTC

Sent 2017-12-12 03:28:50

Shows pending on the exchange I sent it to.

Tried an accelerator service.

moved mempool.dat and flush unconfirmed TX from Bitcoin core and resent, and those new TX don't even show up on blockchain.info.

Tried to rebroadcast TX from https://blockchain.info/pushtx and it gives error:

Parse: Error Parsing Transaction

Have sent another successful transaction from this wallet since as a test.

Don't know what to do now, any help is appreciated.
Jump to: