Topic: Unconfirmed transaction after 14+ hours (Read 3980 times)
Thanks for the information and assistance
I'm no expert but it seems odd that there have been no confirmations after over 14 hours. Its supposed to be a refund on a failed purchase, am I getting scammed somehow?
It made it into block 166559
http://blockexplorer.com/tx/ce9d4ad785f5299eadaba94445f3217d177d67b157b0998c3872795966e5c57a
Ok, that clarifies.
The transaction sending you back 2.5BTC indeed exists, and is unconfirmed: http://bitcoincharts.com/bitcoin/txlist/#ce9d4ad785f5299eadaba94445f3217d177d67b157b0998c3872795966e5c57a
It was sent to you without any fee and is low priority. In addition, it is funded with two other payments that are low priority, not confirmed, and were sent without any fee. Being low priority, all transactions would normally require a minimum .0005 BTC fee for timely inclusion in a block. The first two payments will have to be added to the blockchain before the payment to you could be processed. It may eventually be paid, but only if a miner accepts the zero-fee transactions involved. One may believe that the sender knew there was a low chance of the transaction being accepted and was trying to get you to accept the legitimacy of the non-confirmed payment, which you are under no obligation to accept until it is processed by Bitcoin.
You can also demand the sender re-send the payment from a fully funded wallet with mature coins and include an appropriate fee.
The transaction sending you back 2.5BTC indeed exists, and is unconfirmed: http://bitcoincharts.com/bitcoin/txlist/#ce9d4ad785f5299eadaba94445f3217d177d67b157b0998c3872795966e5c57a
It was sent to you without any fee and is low priority. In addition, it is funded with two other payments that are low priority, not confirmed, and were sent without any fee. Being low priority, all transactions would normally require a minimum .0005 BTC fee for timely inclusion in a block. The first two payments will have to be added to the blockchain before the payment to you could be processed. It may eventually be paid, but only if a miner accepts the zero-fee transactions involved. One may believe that the sender knew there was a low chance of the transaction being accepted and was trying to get you to accept the legitimacy of the non-confirmed payment, which you are under no obligation to accept until it is processed by Bitcoin.
You can also demand the sender re-send the payment from a fully funded wallet with mature coins and include an appropriate fee.
The 1s8Y address is my address that I sent the coins from, it is also the address that I recieve my payments from Slush's pool on. I sent out 2.5 btc to the 1L6dp address as a downpayment on a purchase and yes it nearly emptied my account. I recieve my payments from Slush each time I reach .5 btc which is why there are all the 0.5 chunks I only have 480mhs of mining power).
The seller then had a problem providing me with the account information for the Star Wars the Old Republic account I was purchasing and the account became locked. He sent me the 2.5btc back and that is the transaction information my client recieved in the first post of this thread and that is the transaction in question which still has no confirmations 30 odd hours later.
ce9d4ad785f5299eadaba94445f3217d177d67b157b0998c3872795966e5c57a is the transaction id in question when I search it at blockinfo nothing comes up but somehow it ended up in my logs when I export them to a csv file and it shows as an unconfirmed transaction in my client.
That transaction was sent to me by DiThi and the above quote was his explanation to me about it.
My question is should I just write it off as a scam or is there some other possible explanation?
The seller then had a problem providing me with the account information for the Star Wars the Old Republic account I was purchasing and the account became locked. He sent me the 2.5btc back and that is the transaction information my client recieved in the first post of this thread and that is the transaction in question which still has no confirmations 30 odd hours later.
ce9d4ad785f5299eadaba94445f3217d177d67b157b0998c3872795966e5c57a is the transaction id in question when I search it at blockinfo nothing comes up but somehow it ended up in my logs when I export them to a csv file and it shows as an unconfirmed transaction in my client.
That transaction was sent to me by DiThi and the above quote was his explanation to me about it.
My question is should I just write it off as a scam or is there some other possible explanation?
Is the original poster's receive address 1s8Y - it seems so, if that address is labeled as a "receive from slush" address? If so, then this transaction quoted was not receiving coins, this transaction emptied the address.
In block 166289, 0.5BTC (x5) is sent from 1s8Y7Bv1UkvLHk2B5JLW2tzXPhenC16AS to 1L6dpwtEzQ4TdH3ZRn26MdaHu8aLAK2WnJ, with change going to 1s8Y7Bv1UkvLHk2B5JLW2tzXPhenC16AS. The odd thing is a smaller amount being sent five times in the same transaction from the same address.
It is not sent in a normal way, it is sent in several smaller transactions. Why? Likely because it is under control of the receiving address. The receiving address has received many other odd transactions with multiple inputs from the same address.
The receiving address also has received money from a vanity address 1BountYypWttTvAJcMJVvSRDfX3TJ182To. If we search, we can see that address is used in a tutorial on the strongcoin site for creating offline transactions, in fact that bounty address belongs to forum user strongcoin developer dogisland.
So money was sent in a very strange way out of 1s8Y7, such as someone experimenting with or flooding offline transactions would do, to an address that has also received coins used in an offline transaction generator demo. Probably the original transaction as sent to the network had .5BTC being spent hundreds of times to make sure the wallet was completely tapped out. It is the extra spends in the transaction (the one sent between nodes, not the one included in the blockchain) that the client received that are still unconfirmed.
In block 166289, 0.5BTC (x5) is sent from 1s8Y7Bv1UkvLHk2B5JLW2tzXPhenC16AS to 1L6dpwtEzQ4TdH3ZRn26MdaHu8aLAK2WnJ, with change going to 1s8Y7Bv1UkvLHk2B5JLW2tzXPhenC16AS. The odd thing is a smaller amount being sent five times in the same transaction from the same address.
It is not sent in a normal way, it is sent in several smaller transactions. Why? Likely because it is under control of the receiving address. The receiving address has received many other odd transactions with multiple inputs from the same address.
The receiving address also has received money from a vanity address 1BountYypWttTvAJcMJVvSRDfX3TJ182To. If we search, we can see that address is used in a tutorial on the strongcoin site for creating offline transactions, in fact that bounty address belongs to forum user strongcoin developer dogisland.
So money was sent in a very strange way out of 1s8Y7, such as someone experimenting with or flooding offline transactions would do, to an address that has also received coins used in an offline transaction generator demo. Probably the original transaction as sent to the network had .5BTC being spent hundreds of times to make sure the wallet was completely tapped out. It is the extra spends in the transaction (the one sent between nodes, not the one included in the blockchain) that the client received that are still unconfirmed.
Did you run bitcoin with -rescan ?
Not really sure how to do that. I tried running it from a command prompt and it gave an error about some directory not being released and then when I closed my bitcoin-qt client and my miner it would run but all it did was show a flashing cursor but not respond to any commands after a couple hours I killed it so I could start mining again.
I have emailed the guy and he responded with this:
Quote
Yeah, it seems most nodes have rejected the tx but I still can't send
it again with the same electrum server (it has the unconfirmed
transaction but it's not relaying it...). I'm creating a server
myself, but it's taking forever to populate the database. Meanwhile
I'll try with other servers.
It's my fault for going cheap! Hopefully now the coins are "old
enough" to be sent without fees.
DiThi
it again with the same electrum server (it has the unconfirmed
transaction but it's not relaying it...). I'm creating a server
myself, but it's taking forever to populate the database. Meanwhile
I'll try with other servers.
It's my fault for going cheap! Hopefully now the coins are "old
enough" to be sent without fees.
DiThi
Sounds like a line of bullshit to me but I'm no expert.
According to blockexplorer.com
The address 1s8Y7Bv1UkvLHk2B5JLW2tzXPhenC16AS is empty now
since your tx is not confirmed
You may are under double-spending attack.
The address 1s8Y7Bv1UkvLHk2B5JLW2tzXPhenC16AS is empty now
since your tx is not confirmed
You may are under double-spending attack.
Interesting, maybe doublespending attack?
Did you check the address 1s8Y7Bv1UkvLHk2B5JLW2tzXPhenC16AS on blockexplorer.com ?
The transactions won't show when they are not confirmed, and the ledger will not change too.
Sometimes i prefer this old-school explorer.
Did you check the address 1s8Y7Bv1UkvLHk2B5JLW2tzXPhenC16AS on blockexplorer.com ?
The transactions won't show when they are not confirmed, and the ledger will not change too.
Sometimes i prefer this old-school explorer.
Did you run bitcoin with -rescan ?
its now been over 24 hours and still no confirmations on this transaction anyone have any idea what might be happening?
It's confirmed: http://blockchain.info/tx-index/15439208/fd5e53ceb1102107b9de5da711af489507d11141dda4edc0fe16f8b4dc67bb00
It's probably just your client lagging. What's the latest block you've seen?
It's probably just your client lagging. What's the latest block you've seen?
I believe that is the 2.5btc that I sent out which is showing 154 confirmations in my client, he then returned them after the deal fell thru but that transaction has not confirmed
Try running Bitcoin with -rescan .
I'm at 166448, last recieved block was 51 seconds ago
It's confirmed: http://blockchain.info/tx-index/15439208/fd5e53ceb1102107b9de5da711af489507d11141dda4edc0fe16f8b4dc67bb00
It's probably just your client lagging. What's the latest block you've seen?
It's probably just your client lagging. What's the latest block you've seen?
This is all the information I get if I export it as a csv from bitcoin-qt.
Confirmed: FALSE
Date: 2012-02-11T08:54:39
Type: Received
Label: Slush (wasn't from pool just used the same address)
Address: 1s8Y7Bv1UkvLHk2B5JLW2tzXPhenC16AS
Amount: 2.5
ID: ce9d4ad785f5299eadaba94445f3217d177d67b157b0998c3872795966e5c57a-000
I'm no expert but it seems odd that there have been no confirmations after over 14 hours. Its supposed to be a refund on a failed purchase, am I getting scammed somehow?
Confirmed: FALSE
Date: 2012-02-11T08:54:39
Type: Received
Label: Slush (wasn't from pool just used the same address)
Address: 1s8Y7Bv1UkvLHk2B5JLW2tzXPhenC16AS
Amount: 2.5
ID: ce9d4ad785f5299eadaba94445f3217d177d67b157b0998c3872795966e5c57a-000
I'm no expert but it seems odd that there have been no confirmations after over 14 hours. Its supposed to be a refund on a failed purchase, am I getting scammed somehow?
Jump to: