Author

Topic: 48 hours and still unconfirmed? (Read 1709 times)

legendary
Activity: 2212
Merit: 1199
February 27, 2014, 03:45:43 PM
#26
Hi, i have a problem with Unconfirmed transactions! its 2 low i think! i need a miner please:-!

https://blockchain.info/tx/896fb058376a941b4c7171aa29d2c8360b428213de592b8a0fdc56a3d102c4bc

https://blockchain.info/tx/7fa0a86b067b9b071e717c2753a3b6fa5a336557463af291972f0a5e2b121a0d

these are  no fee transaction ! i don't see the config @my blockchain wallet before i trade!

Please help!


or can someone please record the transaction and send it back so I can trade them with fee?!



55 already Smiley next time do not panic... transaction will be confirmed just sometimes need to wait, and ALWAYS should add a fee !

Smiley
legendary
Activity: 2044
Merit: 1055
February 27, 2014, 10:21:23 AM
#25
Hi, i have a problem with Unconfirmed transactions! its 2 low i think! i need a miner please:-!

https://blockchain.info/tx/896fb058376a941b4c7171aa29d2c8360b428213de592b8a0fdc56a3d102c4bc

https://blockchain.info/tx/7fa0a86b067b9b071e717c2753a3b6fa5a336557463af291972f0a5e2b121a0d

these are  no fee transaction ! i don't see the config @my blockchain wallet before i trade!

Please help!


or can someone please record the transaction and send it back so I can trade them with fee?!



15 confirmations already, what's the problem?
newbie
Activity: 1
Merit: 0
February 27, 2014, 06:21:50 AM
#24
Hi, i have a problem with Unconfirmed transactions! its 2 low i think! i need a miner please:-!

https://blockchain.info/tx/896fb058376a941b4c7171aa29d2c8360b428213de592b8a0fdc56a3d102c4bc

https://blockchain.info/tx/7fa0a86b067b9b071e717c2753a3b6fa5a336557463af291972f0a5e2b121a0d

these are  no fee transaction ! i don't see the config @my blockchain wallet before i trade!

Please help!


or can someone please record the transaction and send it back so I can trade them with fee?!

hero member
Activity: 798
Merit: 1000
January 23, 2014, 04:33:37 PM
#23
I suppose some pools accepts the transaction, and sends it backwards. Otherwise it would be stuck forever in limbo.

This is not hiw bitcoin works. A pool cannot "send it back". There is nowhere to send it to, and they don't have the private key.

The pool either confirms it, or they don't confirm it. There is no way for them to "accept it and send it back"

So then please explain how it was sent back? I honestly don't know lol.

To truly understand, you'd first need to understand that there are no actual "bitcoins" anywhere.  The concept of "a bitcoin" is just an abstraction that we humans use to make it easier to talk about the transfer of control over value.  Your wallet doesn't have any "bitcoins" in it.  There are no "bitcoins" stored on your computer.  Your wallet is just a set of private keys that are used to create digital signatures authorizing a transfer of control.

To show you how "may bitcoins" you have, your wallet converts each of the private keys that it knows about into bitcoin addresses.  Then it scans the entire history of every bitcoin transaction that has ever occurred.  This history is called "the blockchain" and every full node has a complete copy of it.  After scanning through this history, the wallet can determine how many transactions in that history have outputs that are associated with addresses that the wallet knows about, and which of those transaction outputs have not been spent yet.

Yes, I typed that correctly.  You don't spend bitcoins.  You spend transaction outputs.  Once there is a permanent record in the blockchain of a transaction spending the output of a previous transaction, that output can never be spent again.

So, the wallet adds up all the value attributed to these unspent outputs that are associated with addresses that the wallet knows about, and it displays this total as a number of "bitcoins" to you.

When you "send bitcoins", what you actually do is create a transaction that lists some of the unspent outputs that you control to be "spent", and then creates new unspent outputs and associates each new output with a bitcoin address to be a new unspent output.  Then you broadcast this transaction to the bitcoin network and wait for it to be added to the blockchain.

Once it is broadcast, most nodes know about it, so if any of the outputs are associated with addresses that a wallet knows about, the wallet temporarily updates the total that it displays while it waits for the transaction to be added to a block and added to the the blockchain by a miner.  At this point it is seen as having 0 confirmations.

If it never gets confirmed, and if none of the wallets re-broadcast it, eventually each of the nodes drop the transaction out of their memory pool.  When the transaction is no longer in the memory of a wallet, the wallet will no longer know about it so it will no longer include the adjustment in the value that it displays to you.  This means that if you are the "sender", then your wallet will once again include the outputs that you had tried to spend when it displays your value.  It also means that if you are the "receiver", then your wallet will no longer know about the new outputs that were supposed to be associated with your address, so it will stop including that new value in the total that it displays to you.

Since the value displayed by the "sender" wallet increases, and the value displayed by the "receiver" wallet decreases by the same amount, it looks like the transaction was "sent back".  Actually what happened is that the transaction just vanished and no longer exits.

Notice that there are no miners involved in this process at all.

Now, if a miner chooses to "accept" the transaction into a block that they are attempting to mine, and the miner successfully mines and broadcasts the block, then the block will be added to the blockchain and will become part of the permanent record.  In this case, both the "sender" and "receiver" wallets will see the new transaction in the blockchain and will adjust the amount that they display accordingly.  As such, it will "appear" that bitcoins have moved from the "sender" wallet to the "receiver" wallet.  All that really happened though was that a new transaction was added to the blockchain that "spent" previous outputs and created new outputs.

Thanks. I knew that there was no bitcoin "file", just that i didn't know that nodes would eventually "drop out" the transaction.
legendary
Activity: 3472
Merit: 4801
January 23, 2014, 02:58:40 PM
#22
I suppose some pools accepts the transaction, and sends it backwards. Otherwise it would be stuck forever in limbo.

This is not hiw bitcoin works. A pool cannot "send it back". There is nowhere to send it to, and they don't have the private key.

The pool either confirms it, or they don't confirm it. There is no way for them to "accept it and send it back"

So then please explain how it was sent back? I honestly don't know lol.

To truly understand, you'd first need to understand that there are no actual "bitcoins" anywhere.  The concept of "a bitcoin" is just an abstraction that we humans use to make it easier to talk about the transfer of control over value.  Your wallet doesn't have any "bitcoins" in it.  There are no "bitcoins" stored on your computer.  Your wallet is just a set of private keys that are used to create digital signatures authorizing a transfer of control.

To show you how "may bitcoins" you have, your wallet converts each of the private keys that it knows about into bitcoin addresses.  Then it scans the entire history of every bitcoin transaction that has ever occurred.  This history is called "the blockchain" and every full node has a complete copy of it.  After scanning through this history, the wallet can determine how many transactions in that history have outputs that are associated with addresses that the wallet knows about, and which of those transaction outputs have not been spent yet.

Yes, I typed that correctly.  You don't spend bitcoins.  You spend transaction outputs.  Once there is a permanent record in the blockchain of a transaction spending the output of a previous transaction, that output can never be spent again.

So, the wallet adds up all the value attributed to these unspent outputs that are associated with addresses that the wallet knows about, and it displays this total as a number of "bitcoins" to you.

When you "send bitcoins", what you actually do is create a transaction that lists some of the unspent outputs that you control to be "spent", and then creates new unspent outputs and associates each new output with a bitcoin address to be a new unspent output.  Then you broadcast this transaction to the bitcoin network and wait for it to be added to the blockchain.

Once it is broadcast, most nodes know about it, so if any of the outputs are associated with addresses that a wallet knows about, the wallet temporarily updates the total that it displays while it waits for the transaction to be added to a block and added to the the blockchain by a miner.  At this point it is seen as having 0 confirmations.

If it never gets confirmed, and if none of the wallets re-broadcast it, eventually each of the nodes drop the transaction out of their memory pool.  When the transaction is no longer in the memory of a wallet, the wallet will no longer know about it so it will no longer include the adjustment in the value that it displays to you.  This means that if you are the "sender", then your wallet will once again include the outputs that you had tried to spend when it displays your value.  It also means that if you are the "receiver", then your wallet will no longer know about the new outputs that were supposed to be associated with your address, so it will stop including that new value in the total that it displays to you.

Since the value displayed by the "sender" wallet increases, and the value displayed by the "receiver" wallet decreases by the same amount, it looks like the transaction was "sent back".  Actually what happened is that the transaction just vanished and no longer exits.

Notice that there are no miners involved in this process at all.

Now, if a miner chooses to "accept" the transaction into a block that they are attempting to mine, and the miner successfully mines and broadcasts the block, then the block will be added to the blockchain and will become part of the permanent record.  In this case, both the "sender" and "receiver" wallets will see the new transaction in the blockchain and will adjust the amount that they display accordingly.  As such, it will "appear" that bitcoins have moved from the "sender" wallet to the "receiver" wallet.  All that really happened though was that a new transaction was added to the blockchain that "spent" previous outputs and created new outputs.
hero member
Activity: 798
Merit: 1000
January 23, 2014, 01:42:11 PM
#21
I suppose some pools accepts the transaction, and sends it backwards. Otherwise it would be stuck forever in limbo.

This is not hiw bitcoin works. A pool cannot "send it back". There is nowhere to send it to, and they don't have the private key.

The pool either confirms it, or they don't confirm it. There is no way for them to "accept it and send it back"

So then please explain how it was sent back? I honestly don't know lol.
legendary
Activity: 3472
Merit: 4801
January 22, 2014, 10:52:43 PM
#20
I suppose some pools accepts the transaction, and sends it backwards. Otherwise it would be stuck forever in limbo.

This is not how bitcoin works. A pool cannot "send it back". There is nowhere to send it to, and they don't have the private key.

The pool either confirms it, or they don't confirm it. There is no way for them to "accept it and send it back"
hero member
Activity: 798
Merit: 1000
January 22, 2014, 04:29:00 PM
#19
I suppose some pools are nice and take the transaction but reverses it...

Huh

I don't understand what you are trying to say.

I suppose some pools accepts the transaction, and sends it backwards. Otherwise it would be stuck forever in limbo.
legendary
Activity: 3472
Merit: 4801
January 22, 2014, 01:58:34 PM
#18
I suppose some pools are nice and take the transaction but reverses it...

Huh

I don't understand what you are trying to say.
legendary
Activity: 3472
Merit: 4801
January 22, 2014, 01:57:35 PM
#17
Why did it return? Must be the wrong destination address, I assume...

It returned because it wasn't confirmed and both wallets stopped broadcasting it.

That's how bitcoin works
hero member
Activity: 798
Merit: 1000
January 22, 2014, 12:48:01 PM
#16
It is showing up other places - assuming it was 0.0750 BTC  going from 1JJ6QjNpE1DSr7x1wwtLh5TtCk5rm3fhvd to 17oUDTDPgZ961o1sasbYS1YrtWD7ha1UAu .  Is that correct?


It will in all likelihood go through eventually, but with no fee, and no confirmations there are no guarantees as to when.

If you are doing this in the future, it is recommended to always use a fee unless you trust the person or don't care about the length of time to confirm.

You are right about the addresses - and guess what happened!

The BTC was returned to the original senders address! Luckily I paid with PayPal and I am getting my money back..

Well, you are lucky, since the transaction actually got returned.

Why did it return? Must be the wrong destination address, I assume...

I suppose some pools are nice and take the transaction but reverses it...
legendary
Activity: 2044
Merit: 1055
January 22, 2014, 12:14:16 PM
#15
It is showing up other places - assuming it was 0.0750 BTC  going from 1JJ6QjNpE1DSr7x1wwtLh5TtCk5rm3fhvd to 17oUDTDPgZ961o1sasbYS1YrtWD7ha1UAu .  Is that correct?


It will in all likelihood go through eventually, but with no fee, and no confirmations there are no guarantees as to when.

If you are doing this in the future, it is recommended to always use a fee unless you trust the person or don't care about the length of time to confirm.

You are right about the addresses - and guess what happened!

The BTC was returned to the original senders address! Luckily I paid with PayPal and I am getting my money back..

Well, you are lucky, since the transaction actually got returned.

Why did it return? Must be the wrong destination address, I assume...
hero member
Activity: 798
Merit: 1000
January 22, 2014, 12:09:24 PM
#14
The person I bought this Bitcoin from sent without any fee and it's 1520 bytes...is it ever going to confirm :S? Is there any way to speed up the process  Huh



http://blockchain.info/tx-index/c3d5c87fe3afa301cd0c136d18b2eb890cec42574ea1cc99ec9d7dae6358b8a2

Good luck on that, no fee means takes forever...

And actually forever, since it probably won't ever get accepted.
sr. member
Activity: 243
Merit: 250
January 22, 2014, 11:52:30 AM
#13
The person I bought this Bitcoin from sent without any fee and it's 1520 bytes...is it ever going to confirm :S? Is there any way to speed up the process  Huh



http://blockchain.info/tx-index/c3d5c87fe3afa301cd0c136d18b2eb890cec42574ea1cc99ec9d7dae6358b8a2

Good luck on that, no fee means takes forever...
newbie
Activity: 29
Merit: 0
January 22, 2014, 04:08:09 AM
#12
It is showing up other places - assuming it was 0.0750 BTC  going from 1JJ6QjNpE1DSr7x1wwtLh5TtCk5rm3fhvd to 17oUDTDPgZ961o1sasbYS1YrtWD7ha1UAu .  Is that correct?


It will in all likelihood go through eventually, but with no fee, and no confirmations there are no guarantees as to when.

If you are doing this in the future, it is recommended to always use a fee unless you trust the person or don't care about the length of time to confirm.

You are right about the addresses - and guess what happened!

The BTC was returned to the original senders address! Luckily I paid with PayPal and I am getting my money back..

Buying via ebay isn't the way to go Wink
hero member
Activity: 798
Merit: 1000
January 21, 2014, 02:47:19 PM
#11
It is showing up other places - assuming it was 0.0750 BTC  going from 1JJ6QjNpE1DSr7x1wwtLh5TtCk5rm3fhvd to 17oUDTDPgZ961o1sasbYS1YrtWD7ha1UAu .  Is that correct?


It will in all likelihood go through eventually, but with no fee, and no confirmations there are no guarantees as to when.

If you are doing this in the future, it is recommended to always use a fee unless you trust the person or don't care about the length of time to confirm.

You are right about the addresses - and guess what happened!

The BTC was returned to the original senders address! Luckily I paid with PayPal and I am getting my money back..

Well, you are lucky, since the transaction actually got returned.
newbie
Activity: 34
Merit: 0
January 21, 2014, 02:23:54 PM
#10
It is showing up other places - assuming it was 0.0750 BTC  going from 1JJ6QjNpE1DSr7x1wwtLh5TtCk5rm3fhvd to 17oUDTDPgZ961o1sasbYS1YrtWD7ha1UAu .  Is that correct?


It will in all likelihood go through eventually, but with no fee, and no confirmations there are no guarantees as to when.

If you are doing this in the future, it is recommended to always use a fee unless you trust the person or don't care about the length of time to confirm.

You are right about the addresses - and guess what happened!

The BTC was returned to the original senders address! Luckily I paid with PayPal and I am getting my money back..
legendary
Activity: 4228
Merit: 1313
January 20, 2014, 03:52:34 PM
#9
It is showing up other places - assuming it was 0.0750 BTC  going from 1JJ6QjNpE1DSr7x1wwtLh5TtCk5rm3fhvd to 17oUDTDPgZ961o1sasbYS1YrtWD7ha1UAu .  Is that correct?


It will in all likelihood go through eventually, but with no fee, and no confirmations there are no guarantees as to when.

If you are doing this in the future, it is recommended to always use a fee unless you trust the person or don't care about the length of time to confirm.
legendary
Activity: 2394
Merit: 1216
The revolution will be digital
January 20, 2014, 03:36:04 PM
#8
The person I bought this Bitcoin from sent without any fee and it's 1520 bytes...is it ever going to confirm :S? Is there any way to speed up the process  Huh



http://blockchain.info/tx-index/c3d5c87fe3afa301cd0c136d18b2eb890cec42574ea1cc99ec9d7dae6358b8a2

I doubt the TxHash you have posted is real at all. Double check with the counter party if he/she has sent at all as it seems this is an invalid TxHash. tx-indexes are smaller numbers, not so big.
legendary
Activity: 4228
Merit: 1313
January 20, 2014, 03:29:48 PM
#7
The transaction doesn't even show up now on blockchain.info - "Transaction not found".  There are many variables with no fee transactions such as where it was sent from, the pools which have it in memory, the number of transactions waiting etc.
sr. member
Activity: 378
Merit: 255
January 20, 2014, 02:02:09 PM
#6
Elegius supports Child Pay for Parent according to something I read on the internet (can't really confirm).
full member
Activity: 196
Merit: 101
January 20, 2014, 01:20:25 PM
#5
just wait for it, since he didn't pay a fee it's going to take a while..
legendary
Activity: 3472
Merit: 4801
January 20, 2014, 09:08:07 AM
#4
Although it will probably confirm eventually, there is no guarantee that it will ever confirm.

There is no good way to accurately predict how long it will take to confirm, and there is currently no way to speed up the process.

If mining pools would implement "child pays for parent", then they would increase their profitability and there would be a way for you to speed it up.  Unfortunately, I don't know of any mining pools that have implemented "child pays for parent" yet.
newbie
Activity: 34
Merit: 0
January 20, 2014, 07:55:28 AM
#3
A week..damn.
 
Thanks for the response.
legendary
Activity: 1512
Merit: 1012
January 20, 2014, 07:47:50 AM
#2
Fee = 0 ... you have the answer.  Roll Eyes
no fee = long confirmation (in a week).
newbie
Activity: 34
Merit: 0
January 20, 2014, 07:39:31 AM
#1
The person I bought this Bitcoin from sent without any fee and it's 1520 bytes...is it ever going to confirm :S? Is there any way to speed up the process  Huh



http://blockchain.info/tx-index/c3d5c87fe3afa301cd0c136d18b2eb890cec42574ea1cc99ec9d7dae6358b8a2
Jump to: