Topic: 3 Transactions unconfirmed after ~15 hours but new ones ok (Read 4268 times)

The input-transaction-selection algorithm in bitcoin tries to use older transactions, which will have higher priority.

I'd guess that online wallets with lots of users have plenty of old transaction to choose from, so they don't need to pay transaction fees.  Actually, it'd be interesting to try to measure how quickly the average bitcoin in an e-wallet stays in the wallet before being used for an outgoing transaction...

Gotcha, makes sense.

What about sites with online wallets?

most pools include their payments into the blocks they generate. so no fees are needed.

Is there a way to set a transaction fee for payouts from a pool?  I know you can set transaction fees from your bitcoin wallet, but it seems like a majority of the trouble is with transactions not happening from websites, etc.

Are transaction fees something that the pools/websites need to implement themselves to be able to give the user the option?

If there isn't an easy way to ensure that transactions go through quickly, it could be a real deal-killer for bitcoin.  There's far too many people complaining of transactions taking days to happen.  Even for free transactions, that's just ridiculous.  I understand the point about spam, but something needs to be done to ensure that legitimate transactions aren't waiting for more than a couple of hours, in ALL cases.

Because otherwise you can fill a block with pointless spam.

I still have several transactions pending.... why the limit on the size. I heard somewhere that the block has a set number of transactions it can hold, which is ok for now but may scale poorly. why leave open transaction slots in the block?

Did the transactions ever go through?

The miner chooses. Stock Bitcoin limits it to 27 kB of high-priority free transactions. Low-priority transactions only get 4 kB.

What is the limit of free transactions per block? I've been watching off and on over the last 48 hours and I haven't seen it go below 600 and last check it was over 1000.

VERY low priority. My pool payouts from the last three days are still unconfirmed.

Not really. It's based on a priority calculation. Pool payouts tend to be very low priority.

It acts more like a FILO than a FIFO queue.

The number of unconfirmed transactions is the problem. Only so many free transactions are allowed per block. Blocks are still being generated at the normal rate.

Nothing wrong apparently, it's just been a really slow day for free transactions. The worst I've seen in my 2 months bitcoin experience.

For all the people trying to discourage people from buying hardware to mine with it look like we need more. It's been almost 24 hours with no confirmations and the queue at bitcoincharts has been sitting between 600 and 900 unconfirmed transactions for at least the last 24 hours. Looks to me like we need more hardware on the network.

They'll be confirmed eventually.

I am (supposed to be) receiving these coins from a pool server. As far as I can tell my net connect has been stable. All transactions before these processed successfully, others that were in progress are still processing or completed, I have not received any new transactions after these yet, but I sent 2 and they are processing perfectly so far.

This happened to me when I sent coins to mybitcoin.com. My net connection crashed as I sent the tx. The coins were deducted from my wallet but did not appear in mybitcoin. I don't remember if they showed up in that list of unconfirmed transactions. I updated my client from 3.19 to 3.20 and ran bitcoin.exe -rescan. After the blockchain scanned, the transaction did go through automatically.

I can see them on Bitcoin Charts as unconfirmed but new transactions are confirming no problem. How can I find out what's wrong/more info? I can't find any info on Block Explorer with any of this info.

2011-05-05 02:59:52 8db162809270b5a8b9cc6e2935f962546997be43ea291bd546dcccac6cbd18d4 input: 5.94000000 BTC

    5.94000000 BTC from unconfirmed 459223e9d9a530906e9f4ee7f3a40518471bd7b8c71d133bc640f72112dca6c8:0 (1CTiADmVQETfqDEPY2w4VRXp5kjBEedw2)

output: 5.94000000 BTC

    5.25000000 BTC to 1EBRRW84cQFjBesw82UtkgxVDGxXk5jVzt
    0.69000000 BTC to 1HWn2GCfyRkmAWmbUfXTZr5RDWPkynchbY

size: 258 bytes

2011-05-05 02:55:58 6be2e16ee6e3c61d08239ac983f814cecef9ea02588087d8eb2f479cd95c3937 input: 3.47999990 BTC
   
   3.47999990 BTC from unconfirmed a3492cc8a8fecae67f5e4a15f7b83d4d3adc418f6f1c8d4cf3563851dcacee8b:1 (1H8ehcuYRpri2mtTp29ieQ9HewRpLZShRj)

output: 3.47999990 BTC

    2.14999990 BTC to 16GeMZomUTeyCqsqJNivABJ4F8uLKrbuGi
    1.33000000 BTC to 1HWn2GCfyRkmAWmbUfXTZr5RDWPkynchbY

size: 258 bytes


2011-05-05 02:51:25 f2b62323faa340caefc54dc900364cf427897450147983067cd51ba831fd8cb9 input: 1.94000000 BTC

    1.94000000 BTC from unconfirmed f6512be7c83773caf0531e3f0978f1df4aeb3d250e8c98dc559d6f5e732646ac:0 (18BTQm2BkupGDkzDpzsAruDKK7QmSMvCRC)

output: 1.94000000 BTC

    1.12000000 BTC to 1HWn2GCfyRkmAWmbUfXTZr5RDWPkynchbY
    0.82000000 BTC to 1HqWf89T39Q931d9uKB4cgXcEYBFufESEm

size: 257 bytes