|
Title: Transactions stuck for a month Post by: prosperity22 on January 05, 2018, 09:05:47 PM Is anybody able to tell me what the problem is with these transaction?
https://blockchain.info/tx/af7337db5b6b5b3626d3ff6a7eb9866936a8ca2a336ca4e7e553a5aab2a6a7fe https://blockchain.info/tx/d2c8fe92f6f7f76ed967b47e6bfc8a411a5e28f2540c2da95cee6bd9da5c0c0a I tried to put them into an accelerator but it says TXID doesn't exist.. Any help much appreciated. Title: Re: Transactions stuck for a month Post by: mocacinno on January 05, 2018, 10:07:30 PM The reason why they're stuck is simple:
- the fee for both transactions is to low for a decent chance of getting into a block - one of the transactions is using the unspent output from an unconfirmed transaction Why a tx accelerator says it cannot find your txid: - free tx accelerators usually cannot be used on transactions that use inputs they got from unconfirmed transactions - if you broadcasted these tx's a month ago, it's also possible they were dropped from most mempools, which could also explain the accelerator's reaction Which wallet were you using, and are you both sender and receiver, or just the sender/receiver? Title: Re: Transactions stuck for a month Post by: prosperity22 on January 06, 2018, 11:19:12 PM Hi Mocacinno
Thanks for your reply. That was helpful. I am the sender and receiver of both transactions. Both were from my Trezor to a Blockchain.info wallet. I actually tried a different accelerator (BTC.com) and it was able to find both the transactions. It would not accept the one using the unspent output, but says it can accelerate the other for $180. I put it into the Antpool accelerator and am hoping it pushes it through so I don't have to eat the fee. ViaBTC will not detect the transactions. As far as the transaction using the unspent output, what do you think it best option? Title: Re: Transactions stuck for a month Post by: KopikoBrown on January 06, 2018, 11:35:19 PM The first transaction is double spend check this
https://www.blocktrail.com/BTC/tx/af7337db5b6b5b3626d3ff6a7eb9866936a8ca2a336ca4e7e553a5aab2a6a7fe The 2nd transaction is removed or expired https://www.blocktrail.com/BTC/tx/d2c8fe92f6f7f76ed967b47e6bfc8a411a5e28f2540c2da95cee6bd9da5c0c0a Title: Re: Transactions stuck for a month Post by: prosperity22 on January 06, 2018, 11:54:13 PM This is confusing. Blockchain.info says differently. So does my wallet; it shows the balance but as "pending".
https://blockchain.info/tx/d2c8fe92f6f7f76ed967b47e6bfc8a411a5e28f2540c2da95cee6bd9da5c0c0a https://blockchain.info/address/19bfw2P4fHfa4d6QBEkitguMsAN3z6vGfi <--the wallet Title: Re: Transactions stuck for a month Post by: vh on January 07, 2018, 12:18:15 AM these two tx are dead. pending is of no value.
it will expire and be forgotten about at some point in the future. tx1 = af7337db5b6b5b3626d3ff6a7eb9866936a8ca2a336ca4e7e553a5aab2a6a7fe tx2 = d2c8fe92f6f7f76ed967b47e6bfc8a411a5e28f2540c2da95cee6bd9da5c0c0a tx3 = 04272f25818acfcc8e97ab796cb22921bef9725380b185d08feb9a4fe7a05a19 tx -> tx1 -> tx2 tx -> tx3 (double spend of tx (inputs) and confirmed) tx1 is no longer valid, therefore tx2 will never confirm. Title: Re: Transactions stuck for a month Post by: mocacinno on January 07, 2018, 12:20:58 AM This is confusing. Blockchain.info says differently. So does my wallet; it shows the balance but as "pending". https://blockchain.info/tx/d2c8fe92f6f7f76ed967b47e6bfc8a411a5e28f2540c2da95cee6bd9da5c0c0a https://blockchain.info/address/19bfw2P4fHfa4d6QBEkitguMsAN3z6vGfi <--the wallet hmm... I dug some further: the input of d2c8fe92f6f7f76ed967b47e6bfc8a411a5e28f2540c2da95cee6bd9da5c0c0a is vout n 0 of transaction af7337db5b6b5b3626d3ff6a7eb9866936a8ca2a336ca4e7e553a5aab2a6a7fe the inputs of af7337db5b6b5b3626d3ff6a7eb9866936a8ca2a336ca4e7e553a5aab2a6a7fe are vout 1 of transaction 0c268d227af93bd448b17e961399bacc2992c7ddf39f4d6d470eff259890fd36 and vout 56 of b8d21dd69beab619f2617d97412a60f0964c7151a017d2a2a78298ba3cc00e59 blocktrail claims that af7337db5b6b5b3626d3ff6a7eb9866936a8ca2a336ca4e7e553a5aab2a6a7fe is using the same inputs as 04272f25818acfcc8e97ab796cb22921bef9725380b185d08feb9a4fe7a05a19 and they are correct, because if i look it up, the inputs of 04272f25818acfcc8e97ab796cb22921bef9725380b185d08feb9a4fe7a05a19 are vout 1 of transaction 0c268d227af93bd448b17e961399bacc2992c7ddf39f4d6d470eff259890fd36 and vout 56 of transaction b8d21dd69beab619f2617d97412a60f0964c7151a017d2a2a78298ba3cc00e59 I'm pretty tired at the moment, but it seems to be a bug in blockchain.info's block explorer. If the parent transaction af7337db5b6b5b3626d3ff6a7eb9866936a8ca2a336ca4e7e553a5aab2a6a7fe is using the same inputs as transaction 04272f25818acfcc8e97ab796cb22921bef9725380b185d08feb9a4fe7a05a19 (and 04272f25818acfcc8e97ab796cb22921bef9725380b185d08feb9a4fe7a05a19 is confirmed), then af7337db5b6b5b3626d3ff6a7eb9866936a8ca2a336ca4e7e553a5aab2a6a7fe can never confirm, thus any transaction depending on this transaction will never confirm. For the second transaction that was expired/removed (d2c8fe92f6f7f76ed967b47e6bfc8a411a5e28f2540c2da95cee6bd9da5c0c0a) from blocktrail: this is not a big problem, it just means that blocktrails's node removed the transaction from it's mempool... It means it might be high time to either abandon the transaction, or rebroadcast it |