Title: Why is this transaction stuck? Post by: philipma1957 on January 27, 2016, 06:54:13 PM https://blockchain.info/tx/86ac9939ee02a134057acb472a6703251faba6a278219cfdfb6f86227e184045
been stuck for a while more then a few hours. This address sends slow as shit. I get this problem over and over again. it is listed as high priority and it is delaying this transaction. https://blockchain.info/tx/f36c42c7e58d2e75c98ff5551864cfc6bb3292409de5ea3b21930c685a534b62 I put a really high fee here as I hoped some one would pick up both transactions. I get really annoyed at this issue I do not understand why my address https://blockchain.info/address/1JdC6Xg3ajT3rge3FgPNSYYFpmf53Vbtje sends slow. Title: Re: Why is this transaction stuck? Post by: wayniac30 on January 27, 2016, 06:59:35 PM I used to have the same thing.... i think it's because the receiving address spends the unconfirmed bitcoins. I noticed this makes me slow down a lot.
Title: Re: Why is this transaction stuck? Post by: philipma1957 on January 27, 2016, 07:12:26 PM I used to have the same thing.... i think it's because the receiving address spends the unconfirmed bitcoins. I noticed this makes me slow down a lot. It was the same wallet which really fucking annoys me. I pay a fee to switch inside the same wallet for internal account purposes. Now I have 30 plus coins stuck on the second send. This problem is one of BTC's biggest issues. I am going to get into it in detail here. Later today. Title: Re: Why is this transaction stuck? Post by: shorena on January 27, 2016, 07:16:29 PM #1 reasonable fee, check.
Currently estimatefee 1 -> 0.00044328 the TX in question 0.0002 per 2053 so ~0.00009742 estimatefee 15 -> 0.00007770 estimatefee 14 -> 0.00010533 Should thus confirm after ~14-15 blocks according to core. #2 no dust outputs, check. #3 no unconfirmed inputs, check. Should be confirmed in a few hours, I gave it a push. If anyone wants to help, here is the raw TX. Code: 010000000b7c7f817fffcb511e578936a6b73e6c1809ae3cc5b35da4e5f3ed3fb1d4bbced8240000008a47304402205c3b505608aa2d3406368bd60c6e100ac3772152258392693a2de8987094c1e602204af269215bd2c3544f546177d42f81498e7d1ee203905982e8b1b5a08eb78958014104160d9b73ad553e38fb8e469700af8ab89e2d4e34bd5f450775bdd69199f96f34b6183b34044659f66891d925f080758b1c0dd8809c4fa95575dd169b6595960fffffffff1ee97cdc500e32a686c2a27ac45c5a140ca05fd964d73492674a1dd5744aa3d49f0c00008a47304402205b577cf966eb969916e8df2b4e0ef747e4a1122ccb3f770713b921d83d17d73202206c2c8599a9c8d94f60157fe42e487b4fa715d117fe5cb4da54fbf7a5c98abeb7014104160d9b73ad553e38fb8e469700af8ab89e2d4e34bd5f450775bdd69199f96f34b6183b34044659f66891d925f080758b1c0dd8809c4fa95575dd169b6595960fffffffff62809e670d242ccea70e81e7217a183a8cb6f35d6293e916f0af3614ee12a6faa60c00008b483045022100a21f111f395cc01218298bb552ff0d6c52666d0eccf24c9387f409db48366d3b02201d94261a35787fbff255b09452caf5f6de9f14a6bdc69e7439c807c40d97bd82014104160d9b73ad553e38fb8e469700af8ab89e2d4e34bd5f450775bdd69199f96f34b6183b34044659f66891d925f080758b1c0dd8809c4fa95575dd169b6595960fffffffffaf18251bad88ca34b2e6f82d2d092da3df84cd4e1951c5b525b3ad8af68844e1010000008a473044022023193893c7f5ee46739bfc6cb6425cc3b4d64e6b32271cad706d811adcfbae520220172051d18dac6eb5e6098c8d2c2f1851f04f024069cb35eabdf633f39fdbd0ab014104160d9b73ad553e38fb8e469700af8ab89e2d4e34bd5f450775bdd69199f96f34b6183b34044659f66891d925f080758b1c0dd8809c4fa95575dd169b6595960fffffffff29ae4bf020f47584e6b858aa6bb8be030883f8c596b238cf273e32c25e1fc48f920d00008a473044022034e2b94f612a72123133d6dd99f419dc4131b612af3fac4f207a8a7c58023951022031e3fdabc0a40677b728cd25bc9d7295716f31ece5e45ace60d8e063d0d8695d014104160d9b73ad553e38fb8e469700af8ab89e2d4e34bd5f450775bdd69199f96f34b6183b34044659f66891d925f080758b1c0dd8809c4fa95575dd169b6595960fffffffff8fec49c027961c67963b8cdde9afe1c4d6e874fa6c7115f3703569020e8ac36d010000008b483045022100c870ac4defbe8b3d779555a2303b959397caabeb1ea99142f1b877c5e9efb39602200c4c796bb0777cc7a5cb3e55ae14fd81822a89d805b3308fa609d453243c6b46014104160d9b73ad553e38fb8e469700af8ab89e2d4e34bd5f450775bdd69199f96f34b6183b34044659f66891d925f080758b1c0dd8809c4fa95575dd169b6595960fffffffffbc4fa4d298e0e0037066079117bd7b0dd6697a7014ece0bd701598eae61358ef200000008b483045022100c66880417f782a9bbf6e3e282eaa1658c57382b609360353b694bdc7668f885a02205449ea559a7244043c79ca50f1c1b774c9921a6b7349f64f0b44926f4b202415014104160d9b73ad553e38fb8e469700af8ab89e2d4e34bd5f450775bdd69199f96f34b6183b34044659f66891d925f080758b1c0dd8809c4fa95575dd169b6595960fffffffff4f14eea513138426aab584fbcf524fe243329ac233d098ac4c82f10b80ede458010000008a4730440220592eaf7442a4336b315cab97e451bf58b6292b96ee92f86c41c4212d5641681a022033a3471bdcf2fc2a34c2fb6f6cfe390601b18ad2ff87ecea0a08bec1397641bd014104160d9b73ad553e38fb8e469700af8ab89e2d4e34bd5f450775bdd69199f96f34b6183b34044659f66891d925f080758b1c0dd8809c4fa95575dd169b6595960fffffffffc45614e425690c7e581fb47fcffb65a0a3a61c86b882a18e2b1c2cf85187e8e6010000008b483045022100dcc8ea0d921fe5b6e6e556b33a1504598f9191d3b81c674d225e7a70e62ba58a02200e5f356b4e658af872e7a23b89264be6193c2dd34de55a493ab4238352b82d72014104160d9b73ad553e38fb8e469700af8ab89e2d4e34bd5f450775bdd69199f96f34b6183b34044659f66891d925f080758b1c0dd8809c4fa95575dd169b6595960fffffffff2f2ad9ba5ce752ceb8f75701399b356a451f761a46cf69213a4da407b2103f53010000008b483045022100ed89319d8bd27f20cdfbf250481c1f2eca4cade02ef02b22352db88a662019d802200afb7e378b4ca9ff4ea6fb7dbe2d7ffa5528b86e290aaec483fe1c166a85dbe3014104160d9b73ad553e38fb8e469700af8ab89e2d4e34bd5f450775bdd69199f96f34b6183b34044659f66891d925f080758b1c0dd8809c4fa95575dd169b6595960fffffffff2c24e3c47ef90e5dcb3a65a21cafc9f857c83af13e5184e61c2da318c16c8beb010000008b4830450221009a04b3484e9f23ab971b633c0b1264db7ac8bddac7b17e596bc401034549799c02202083cacdfd108c587b148414104dcd2fc3b4694f537aad284a4fdf7e58bccaee014104160d9b73ad553e38fb8e469700af8ab89e2d4e34bd5f450775bdd69199f96f34b6183b34044659f66891d925f080758b1c0dd8809c4fa95575dd169b6595960fffffffff02c068ad10000000001976a91470c735cb47fb02ba9b205b7a42cf77465c175e7d88acc78f1b05000000001976a914c1525ff6ca960773a033a330b4674c6e91dff8f588ac00000000 Title: Re: Why is this transaction stuck? Post by: wayniac30 on January 27, 2016, 09:16:12 PM Got the same problem.... again...
https://blockchain.info/tx/d1de744a8a0515d209b60cbfeb9c3ac50c2e64058cf87e7405279413cf622d3f Title: Re: Why is this transaction stuck? Post by: shorena on January 27, 2016, 09:36:14 PM Got the same problem.... again... https://blockchain.info/tx/d1de744a8a0515d209b60cbfeb9c3ac50c2e64058cf87e7405279413cf622d3f Thats confirmed though. Title: Re: Why is this transaction stuck? Post by: wayniac30 on January 27, 2016, 09:44:10 PM Got the same problem.... again... https://blockchain.info/tx/d1de744a8a0515d209b60cbfeb9c3ac50c2e64058cf87e7405279413cf622d3f Thats confirmed though. Yeah it did now... took over 30 mins though with fee higher as recommended. Very weird that happens a lot to me somehow. Title: Re: Why is this transaction stuck? Post by: philipma1957 on January 27, 2016, 09:56:23 PM Got the same problem.... again... https://blockchain.info/tx/d1de744a8a0515d209b60cbfeb9c3ac50c2e64058cf87e7405279413cf622d3f Thats confirmed though. Yeah it did now... took over 30 mins though with fee higher as recommended. Very weird that happens a lot to me somehow. I suspect there is a flag against addresses. my address is old and has had 1000 plus transactions. It is now more then 23 blocks and more then 5 hours since my tx id was done I would not be so annoyed but it now has locked up a new transaction of 30 plus coins. I also am annoyed since the first transaction should be instant and free. this address https://blockchain.info/address/1JdC6Xg3ajT3rge3FgPNSYYFpmf53Vbtje is the old address with 1328 transactions dating back to 2012 this address is newer https://blockchain.info/address/1BHKKrAh5oTacQnmjfACXjE9cGyFRR8rVD but in the same wallet. So I did a transfer within my own wallet. I spent 0.0002 to do it and All my funds are frozen. Along with 28 coins from other people Not good. here is proof it is between the same wallet https://i.imgur.com/qlLwKXP.png Title: Re: Why is this transaction stuck? Post by: wayniac30 on January 27, 2016, 09:59:18 PM I suspect there is a flag against addresses. Makes me think.... you mean they "flag" old addresses? I'm not following you on this one... Title: Re: Why is this transaction stuck? Post by: achow101 on January 27, 2016, 10:05:43 PM I suspect there is a flag against addresses. There is not. Nothing "flags" an address for being old or prevents an old address from spending.The problem here is the size of the transaction. As Shorena said, the fee isn't sufficient for a transaction of this size. All you can do is wait. You could attempt a double spend transaction which would simply boost the fee (an RBF transaction). Basically you just need to send the transaction again but with a higher fee. Title: Re: Why is this transaction stuck? Post by: philipma1957 on January 27, 2016, 10:12:49 PM I suspect there is a flag against addresses. There is not. Nothing "flags" an address for being old or prevents an old address from spending.The problem here is the size of the transaction. As Shorena said, the fee isn't sufficient for a transaction of this size. All you can do is wait. You could attempt a double spend transaction which would simply boost the fee (an RBF transaction). Basically you just need to send the transaction again but with a higher fee. so what should 2.79 coins cost to transfer? and while I am at what should 30 coins cost to move? Title: Re: Why is this transaction stuck? Post by: wayniac30 on January 27, 2016, 10:17:22 PM I suspect there is a flag against addresses. There is not. Nothing "flags" an address for being old or prevents an old address from spending.The problem here is the size of the transaction. As Shorena said, the fee isn't sufficient for a transaction of this size. All you can do is wait. You could attempt a double spend transaction which would simply boost the fee (an RBF transaction). Basically you just need to send the transaction again but with a higher fee. so what should 2.79 coins cost to transfer? and while I am at what should 30 coins cost to move? I did notice when you use a wallet with a lot of addresses the coins get spread all over those addresses which makes one transaction rather large in size because some wallets generate a lot of inputs. Example: https://blockchain.info/tx/86ac9939ee02a134057acb472a6703251faba6a278219cfdfb6f86227e184045 Input scripts: Code: Input Scripts Size 2053 (bytes) - Transaction fee less than recommended Some wallets don't actually calculate this correct causing a transaction to look fine on the fees but they are actually to low because of the many inputs. Solution: Set your standard fee to 120% Title: Re: Why is this transaction stuck? Post by: Nybbas on January 27, 2016, 10:27:27 PM So after all bitcoin is far from perfect? How this can be solved?
Title: Re: Why is this transaction stuck? Post by: wayniac30 on January 27, 2016, 10:28:29 PM So after all bitcoin is far from perfect? How this can be solved? Solution: Set your standard fee to 120% or more. I do 150% on some wallets with a lot of addresses. Title: Re: Why is this transaction stuck? Post by: wayniac30 on January 27, 2016, 10:30:35 PM By the way you could ask users like "knightdk" to push your transaction, gets confirmed very fast.
Title: Re: Why is this transaction stuck? Post by: AliceWonderMiscreations on January 27, 2016, 10:35:43 PM So after all bitcoin is far from perfect? How this can be solved? It's not bitcoin that is the problem, it is your wallet software. Title: Re: Why is this transaction stuck? Post by: achow101 on January 27, 2016, 10:44:50 PM I suspect there is a flag against addresses. There is not. Nothing "flags" an address for being old or prevents an old address from spending.The problem here is the size of the transaction. As Shorena said, the fee isn't sufficient for a transaction of this size. All you can do is wait. You could attempt a double spend transaction which would simply boost the fee (an RBF transaction). Basically you just need to send the transaction again but with a higher fee. so what should 2.79 coins cost to transfer? and while I am at what should 30 coins cost to move? I use this site: http://www.cointape.com/ to calculate fees. It does it in satoshis per byte. Title: Re: Why is this transaction stuck? Post by: ranochigo on January 27, 2016, 10:54:05 PM So after all bitcoin is far from perfect? How this can be solved? Solution: Set your standard fee to 120% or more. I do 150% on some wallets with a lot of addresses. By the way you could ask users like "knightdk" to push your transaction, gets confirmed very fast. Rebroadcasting does not ensure that it will definitely confirm soon. It would still require a miner that is willing to accept it. It would allow for miners to see your TX and even include it if they hadn't or has dropped it out of the mempool.Here's the raw tx: Code: 010000000b7c7f817fffcb511e578936a6b73e6c1809ae3cc5b35da4e5f3ed3fb1d4bbced8240000008a47304402205c3b505608aa2d3406368bd60c6e100ac3772152258392693a2de8987094c1e602204af269215bd2c3544f546177d42f81498e7d1ee203905982e8b1b5a08eb78958014104160d9b73ad553e38fb8e469700af8ab89e2d4e34bd5f450775bdd69199f96f34b6183b34044659f66891d925f080758b1c0dd8809c4fa95575dd169b6595960fffffffff1ee97cdc500e32a686c2a27ac45c5a140ca05fd964d73492674a1dd5744aa3d49f0c00008a47304402205b577cf966eb969916e8df2b4e0ef747e4a1122ccb3f770713b921d83d17d73202206c2c8599a9c8d94f60157fe42e487b4fa715d117fe5cb4da54fbf7a5c98abeb7014104160d9b73ad553e38fb8e469700af8ab89e2d4e34bd5f450775bdd69199f96f34b6183b34044659f66891d925f080758b1c0dd8809c4fa95575dd169b6595960fffffffff62809e670d242ccea70e81e7217a183a8cb6f35d6293e916f0af3614ee12a6faa60c00008b483045022100a21f111f395cc01218298bb552ff0d6c52666d0eccf24c9387f409db48366d3b02201d94261a35787fbff255b09452caf5f6de9f14a6bdc69e7439c807c40d97bd82014104160d9b73ad553e38fb8e469700af8ab89e2d4e34bd5f450775bdd69199f96f34b6183b34044659f66891d925f080758b1c0dd8809c4fa95575dd169b6595960fffffffffaf18251bad88ca34b2e6f82d2d092da3df84cd4e1951c5b525b3ad8af68844e1010000008a473044022023193893c7f5ee46739bfc6cb6425cc3b4d64e6b32271cad706d811adcfbae520220172051d18dac6eb5e6098c8d2c2f1851f04f024069cb35eabdf633f39fdbd0ab014104160d9b73ad553e38fb8e469700af8ab89e2d4e34bd5f450775bdd69199f96f34b6183b34044659f66891d925f080758b1c0dd8809c4fa95575dd169b6595960fffffffff29ae4bf020f47584e6b858aa6bb8be030883f8c596b238cf273e32c25e1fc48f920d00008a473044022034e2b94f612a72123133d6dd99f419dc4131b612af3fac4f207a8a7c58023951022031e3fdabc0a40677b728cd25bc9d7295716f31ece5e45ace60d8e063d0d8695d014104160d9b73ad553e38fb8e469700af8ab89e2d4e34bd5f450775bdd69199f96f34b6183b34044659f66891d925f080758b1c0dd8809c4fa95575dd169b6595960fffffffff8fec49c027961c67963b8cdde9afe1c4d6e874fa6c7115f3703569020e8ac36d010000008b483045022100c870ac4defbe8b3d779555a2303b959397caabeb1ea99142f1b877c5e9efb39602200c4c796bb0777cc7a5cb3e55ae14fd81822a89d805b3308fa609d453243c6b46014104160d9b73ad553e38fb8e469700af8ab89e2d4e34bd5f450775bdd69199f96f34b6183b34044659f66891d925f080758b1c0dd8809c4fa95575dd169b6595960fffffffffbc4fa4d298e0e0037066079117bd7b0dd6697a7014ece0bd701598eae61358ef200000008b483045022100c66880417f782a9bbf6e3e282eaa1658c57382b609360353b694bdc7668f885a02205449ea559a7244043c79ca50f1c1b774c9921a6b7349f64f0b44926f4b202415014104160d9b73ad553e38fb8e469700af8ab89e2d4e34bd5f450775bdd69199f96f34b6183b34044659f66891d925f080758b1c0dd8809c4fa95575dd169b6595960fffffffff4f14eea513138426aab584fbcf524fe243329ac233d098ac4c82f10b80ede458010000008a4730440220592eaf7442a4336b315cab97e451bf58b6292b96ee92f86c41c4212d5641681a022033a3471bdcf2fc2a34c2fb6f6cfe390601b18ad2ff87ecea0a08bec1397641bd014104160d9b73ad553e38fb8e469700af8ab89e2d4e34bd5f450775bdd69199f96f34b6183b34044659f66891d925f080758b1c0dd8809c4fa95575dd169b6595960fffffffffc45614e425690c7e581fb47fcffb65a0a3a61c86b882a18e2b1c2cf85187e8e6010000008b483045022100dcc8ea0d921fe5b6e6e556b33a1504598f9191d3b81c674d225e7a70e62ba58a02200e5f356b4e658af872e7a23b89264be6193c2dd34de55a493ab4238352b82d72014104160d9b73ad553e38fb8e469700af8ab89e2d4e34bd5f450775bdd69199f96f34b6183b34044659f66891d925f080758b1c0dd8809c4fa95575dd169b6595960fffffffff2f2ad9ba5ce752ceb8f75701399b356a451f761a46cf69213a4da407b2103f53010000008b483045022100ed89319d8bd27f20cdfbf250481c1f2eca4cade02ef02b22352db88a662019d802200afb7e378b4ca9ff4ea6fb7dbe2d7ffa5528b86e290aaec483fe1c166a85dbe3014104160d9b73ad553e38fb8e469700af8ab89e2d4e34bd5f450775bdd69199f96f34b6183b34044659f66891d925f080758b1c0dd8809c4fa95575dd169b6595960fffffffff2c24e3c47ef90e5dcb3a65a21cafc9f857c83af13e5184e61c2da318c16c8beb010000008b4830450221009a04b3484e9f23ab971b633c0b1264db7ac8bddac7b17e596bc401034549799c02202083cacdfd108c587b148414104dcd2fc3b4694f537aad284a4fdf7e58bccaee014104160d9b73ad553e38fb8e469700af8ab89e2d4e34bd5f450775bdd69199f96f34b6183b34044659f66891d925f080758b1c0dd8809c4fa95575dd169b6595960fffffffff02c068ad10000000001976a91470c735cb47fb02ba9b205b7a42cf77465c175e7d88acc78f1b05000000001976a914c1525ff6ca960773a033a330b4674c6e91dff8f588ac00000000 You can go sites listed here:https://en.bitcoin.it/wiki/Transaction_broadcasting and paste the entire code in to rebroadcast. Title: Re: Why is this transaction stuck? Post by: philipma1957 on January 27, 2016, 11:52:15 PM I suspect there is a flag against addresses. There is not. Nothing "flags" an address for being old or prevents an old address from spending.The problem here is the size of the transaction. As Shorena said, the fee isn't sufficient for a transaction of this size. All you can do is wait. You could attempt a double spend transaction which would simply boost the fee (an RBF transaction). Basically you just need to send the transaction again but with a higher fee. so what should 2.79 coins cost to transfer? and while I am at what should 30 coins cost to move? I use this site: http://www.cointape.com/ to calculate fees. It does it in satoshis per byte. I am confused as to your estimate I paid 0.0002 already. The two addresses are within the same wallet. So to push this I need 0.00011 extra ? If so How do I add this 0.00011 extra. better yet can you push it for a reasonable fee> say .005 Title: Re: Why is this transaction stuck? Post by: achow101 on January 27, 2016, 11:56:38 PM I am confused as to your estimate I paid 0.0002 already. The entire fee should have been 0.0011The two addresses are within the same wallet. So to push this I need 0.00011 extra ? If so How do I add this 0.00011 extra. you must create a second transaction which spends exactly those same inputs just that one of the outputs has slightly less so that the fee is high enough.I can make it for you, you just need to sign the unsigned transaction which I will create. Edit: sorry, I had 1 too many zeros. The fee should be 110000 satoshis Edit2: here is your unsigned transaction: Code: 010000000b7c7f817fffcb511e578936a6b73e6c1809ae3cc5b35da4e5f3ed3fb1d4bbced82400000000ffffffff1ee97cdc500e32a686c2a27ac45c5a140ca05fd964d73492674a1dd5744aa3d49f0c000000ffffffff62809e670d242ccea70e81e7217a183a8cb6f35d6293e916f0af3614ee12a6faa60c000000ffffffffaf18251bad88ca34b2e6f82d2d092da3df84cd4e1951c5b525b3ad8af68844e10100000000ffffffff29ae4bf020f47584e6b858aa6bb8be030883f8c596b238cf273e32c25e1fc48f920d000000ffffffff8fec49c027961c67963b8cdde9afe1c4d6e874fa6c7115f3703569020e8ac36d0100000000ffffffffbc4fa4d298e0e0037066079117bd7b0dd6697a7014ece0bd701598eae61358ef2000000000ffffffff4f14eea513138426aab584fbcf524fe243329ac233d098ac4c82f10b80ede4580100000000ffffffffc45614e425690c7e581fb47fcffb65a0a3a61c86b882a18e2b1c2cf85187e8e60100000000ffffffff2f2ad9ba5ce752ceb8f75701399b356a451f761a46cf69213a4da407b2103f530100000000ffffffff2c24e3c47ef90e5dcb3a65a21cafc9f857c83af13e5184e61c2da318c16c8beb0100000000ffffffff02c068ad10000000001976a91470c735cb47fb02ba9b205b7a42cf77465c175e7d88ac37301a05000000001976a914c1525ff6ca960773a033a330b4674c6e91dff8f588ac00000000 Title: Re: Why is this transaction stuck? Post by: philipma1957 on January 28, 2016, 12:28:53 AM I am confused as to your estimate I paid 0.0002 already. The entire fee should have been 0.0011The two addresses are within the same wallet. So to push this I need 0.00011 extra ? If so How do I add this 0.00011 extra. you must create a second transaction which spends exactly those same inputs just that one of the outputs has slightly less so that the fee is high enough.I can make it for you, you just need to sign the unsigned transaction which I will create. Edit: sorry, I had 1 too many zeros. The fee should be 110000 satoshis My other option would be wait for my wallet to kick out the tranaction correct? This happened one or two other times. I did not realize the size of the transaction referred to bytes not btc. Title: Re: Why is this transaction stuck? Post by: achow101 on January 28, 2016, 12:37:07 AM My other option would be wait for my wallet to kick out the tranaction correct? Yes. Since it looks like you are using blockchain.info (IMHO that is a bad idea), they will drop the transaction after 3 days.This happened one or two other times. I did not realize the size of the transaction referred to bytes not btc. Yes, that is a common misconception. Title: Re: Why is this transaction stuck? Post by: philipma1957 on January 28, 2016, 12:46:27 AM My other option would be wait for my wallet to kick out the tranaction correct? Yes. Since it looks like you are using blockchain.info (IMHO that is a bad idea), they will drop the transaction after 3 days.This happened one or two other times. I did not realize the size of the transaction referred to bytes not btc. Yes, that is a common misconception. Not much other choice But to wait. Title: Re: Why is this transaction stuck? Post by: achow101 on January 28, 2016, 12:52:17 AM My other option would be wait for my wallet to kick out the tranaction correct? Yes. Since it looks like you are using blockchain.info (IMHO that is a bad idea), they will drop the transaction after 3 days.This happened one or two other times. I did not realize the size of the transaction referred to bytes not btc. Yes, that is a common misconception. Not much other choice But to wait. Title: Re: Why is this transaction stuck? Post by: philipma1957 on January 28, 2016, 01:05:16 AM My other option would be wait for my wallet to kick out the tranaction correct? Yes. Since it looks like you are using blockchain.info (IMHO that is a bad idea), they will drop the transaction after 3 days.This happened one or two other times. I did not realize the size of the transaction referred to bytes not btc. Yes, that is a common misconception. Not much other choice But to wait. It cleared a few minutes ago. Thanks for help. Title: Re: Why is this transaction stuck? Post by: antonlevay on January 28, 2016, 11:41:03 AM I had the exact same problem, this thread helped me out a lot. Thank you!
|