Slow transaction 17h, please checked whats going on

[cfbit]

Hey guy newbie here iv been using btc since the begining of the year and usally a couple of transactions a day, but iv never seen this iv got a transactions with 0/6 comfirmation and its now 17 hours please help me out

txid edeef69cb97942d490e2961a54f689d55392d1d5a0606f25fa6abce26f662c80

address 1KZvXiKLhmziQFCSBXXXj8d6M2o11ADfve

[1714917848]

1714917848

[1714917848]

1714917848

[1714917848]

1714917848

[pedrog]

There's a problem with your transaction propagation:

https://blockchain.info/pt/address/1KZvXiKLhmziQFCSBXXXj8d6M2o11ADfve
https://btc.com/1KZvXiKLhmziQFCSBXXXj8d6M2o11ADfve
https://blockr.io/address/info/1KZvXiKLhmziQFCSBXXXj8d6M2o11ADfve

Transaction may not exist or it was double spent.

[cfbit]

what can i do about it, its going to my wallet so it shouldn't be spent

[mocacinno]

what can i do about it, its going to my wallet so it shouldn't be spent

So, the output of the transaction will be spendable by you? In other words: are you the receiver?
If you're the sender, you could just double spend the inputs from transaction edeef69cb97942d490e2961a54f689d55392d1d5a0606f25fa6abce26f662c80 to create a new transaction, if you're the receiver you should get your hands on the raw, signed transaction, or you could contact the sender... I've checked, and the signed transaction wasn't in my mempool either, so i can't really help you...

Could you also tell us which wallet software you're using?

[cfbit]

ok well its going from my bitsler account to my coinjar wallet, bitsler just say there's nothing they can do and to just wait 

[ranochigo]

Your transaction pays a fee of 108 satoshi per byte, below the current average of 180 satoshi per byte. It can take sometime to confirm or else you can follow mocacinno. If the propagation isn't good, it is easy to just craft an alternative conflicting transaction.

I've obtained your raw transaction, it is

Code:

01000000017b8d3cc308b28000dfa49a87fe68923c953839613ad9c0eb14104917d8c6b86301000000da00473044022079d1e094c66f5a6dfd609b84ce8a939394b933458730cc5d33fc3018ac0c9190022010e9c1ec641384ea17e091be1e25fcb574f8d167491b47886f153adbb1cfe72701483045022100d0616eca7bcccef1f9ca07185cc4bf09867538a8d86335111495e185fae5ed0d022037bd1424350315738a320ac75056de6d6e4e87cefaccf4eecf260c89cf14041f01475221039cdcb27d498db494159901ab4a5e93c27f54dc80f0f9b3de9d815e97f6679c5321022df113c0a7331ef2e279648fced275d96c460ae90f71a95c913550701392101a52aeffffffff0250f96e01000000001976a914cbac4253218f2d85631d2151985d6e9b065437b688ac758dd9490000000017a914c1006dc4b0b4eca6ea9272a8e052583514a5f7208700000000

I've helped you to rebroadcast it to ensure a better propagation. You can do it periodically at coinb.in/#broadcast.

[cfbit]

thanks i will use a higher fee next time, so it will comfirm i just need to wait

[HCP]

The fees look "Ok"... not huge, but not like 10sats/byte or anything... I think the real problem is that your transaction is at the end of a MASSIVE chain of unconfirmed transactions (in reverse order):

edeef69cb97942d490e2961a54f689d55392d1d5a0606f25fa6abce26f662c80
63b8c6d817491014ebc0d93a613938953c9268fe879aa4df0080b208c33c8d7b
9bc76be2f3fd59ad1ce0c979f25e29bc66cf1c9b6e312ed73ddabd30af1121ea
574078779b3fe1864e59d1ee523ea2fecdfda731c22815f66dc9643106a88f19
24c6590c9e0ecda4e540b93289ceb3be2340b08eeead1034356755b6f213e48c
b8eff59bf1420ea5f1e942ccc8a42e2d4077e59c83cd132ce4b3df65cdf95f0d
ab4c0708075a4ffea3d7412a91559cdaf28299b687c94ec354cbf157d62ba2e5
6db892685c8a37f070fb66075b6326a426422cb221cd4b6070db6f5898faa19d
d0893ce9a454e54c2b5bc91969dbb945ecd084310230ad5128320e37964d431b
cacf8172ad1ed7f335a08cd83e37c458d31c8474cd2dab741e6f1d81e6cac17c
c5479691cfb69563d57e85ecf80589ff0d903b4898ebc2940107dbe236a5ec1e
b6834fe82bf72fbcf2b548ce22dd6576568e9d3a3313fe110227f071c5f9f167
6216e06f75201ed3f873043ae6ba1fa641090e7abaf665229de6095bba346c08
efbbd9fc3cad1f4f939c9e75d11bd112d88807cd58f443c9c2faaa73801f165b
4f6d62bf361b598372c540be4e72ad757e2a0c494ec60bb781fa75be8cdbf804
dfcca2299409609fc2d876ecd116312b65e376f88586625a0fe0a8118323b2df
1928e17f2bd27c6e93e14a3fe6c6a96925a6fdd2ada9d0d42a106cff6a1c9c88
f5b83958410052849af7a02b0e904fa4b1d59fc2597ccc05c1377e89fe892971
e3003a2c0a7fcb076cbb7334b0a1d8f68e7ffbaa89f582e07fba593c5372efb6
cde6fd475130b8b7f1f7d92f05af2eb107656de30fc48e4bbc08b3183cc53a70
607a3a3a557fa0d25b4eca42c857c714a543841f51b25af15089d9057c11cd6e
f0eefc04730d9a762f28c42d03213132f453a840accd5e4d74acf4fc83f293c1
58ab206a5d4babf677368e16a906a099620836a5bd43c3c5d877bf03e395da83
faa839b2614d8ac437a897ee5a2a5f3c61dcba9dc55b02a130764e4c5ff93f0f
5f31b3c2b3f6f97932f2e4ed8575e4ec87f85f954b1e90271104e0cd4f5b1cfe
fa77ab7911df34a8fb131e09bc7a6c6551e8e4630ba7f49528dc3aae55a23b46 - 1 Confirmation

If you can't be bothered counting, your transaction is #25... So, until all of those other 24 transactions get confirmed... your transaction will be waiting

And bitsler are technically correct, they can't do anything NOW... however, they could avoid all this by trying to batch their transactions and use "Pay To Many" instead of sending them one at a time in a big long chain like this...

Mind you, if they did that, people would moan that withdrawls took too long or claim they were scam because their withdraw didn't process "instantly"