Bitcoin Forum
April 19, 2024, 04:15:20 AM *
News: Latest Bitcoin Core release: 26.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Transaction sent 7 hours ago still unconfirmed?  (Read 1328 times)
omgitsmehehe (OP)
Full Member
***
Offline Offline

Activity: 580
Merit: 108



View Profile
April 19, 2013, 11:30:18 PM
 #1

Hey everyone,

I sent a transaction to an address 7 hours ago and it is still showing as unconfirmed.... I paid the 0.00001BTC (I don't know fee exactly but when it asked for fee I just said yes)

https://blockchain.info/address/12nx3qqkySaEEhuRJg3B9qDiLhwz4XAiXk

Any ideas?

EDIT: Also, I sent 0.38BTC to SatoshiDice about 10 mins ago and that has 2 confirmations already. (Paid the exact same fee).

1713500120
Hero Member
*
Offline Offline

Posts: 1713500120

View Profile Personal Message (Offline)

Ignore
1713500120
Reply with quote  #2

1713500120
Report to moderator
The grue lurks in the darkest places of the earth. Its favorite diet is adventurers, but its insatiable appetite is tempered by its fear of light. No grue has ever been seen by the light of day, and few have survived its fearsome jaws to tell the tale.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
Stephen Gornick
Legendary
*
Offline Offline

Activity: 2506
Merit: 1010


View Profile
April 20, 2013, 04:11:01 AM
 #2

Any ideas?

Well, you didn't specificy which transaction, just the address. 

This transaction didn't have any fee paid
 - https://blockchain.info/tx/53997b4c90953afd79c0cda631e93a32a51e494350daa7c384390a7499942329

The reason it needed a fee is because of the details of the transaction.  If you look at the transaction in Advanced mode (scroll to bottom, click Advanced), then the transaction will show link to see the previous outputs.

Many of the INPUTs for your transaction either hand't confirmed yet at the time you made the transction or had just recently confirmed (e.g. 21 blocks prior).

That is the type of activity that would also come from someone trying to harm the bitcoin network, so the Bitcoin miners consider that to be a low priority transaction.


Unichange.me

            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █


omgitsmehehe (OP)
Full Member
***
Offline Offline

Activity: 580
Merit: 108



View Profile
April 22, 2013, 10:22:25 AM
 #3

Oh I see. What is the recommended fee?


Stephen Gornick
Legendary
*
Offline Offline

Activity: 2506
Merit: 1010


View Profile
April 23, 2013, 08:55:11 PM
 #4

Oh I see. What is the recommended fee?

Well, to avoid the transaction being considered "low priority" a fee of 0.0005 BTC would do that.  Additionally, if the transaction is larger (greater than 10K bytes) the fee can be higher.

Unichange.me

            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █


J.Socal
Hero Member
*****
Offline Offline

Activity: 495
Merit: 500



View Profile
April 24, 2013, 05:06:00 PM
 #5

Also make sure your btc client is uptodate
Loozik
Sr. Member
****
Offline Offline

Activity: 378
Merit: 250


Born to chew bubble gum and kick ass


View Profile
April 25, 2013, 01:02:37 PM
 #6

Well, to avoid the transaction being considered "low priority" a fee of 0.0005 BTC would do that.  Additionally, if the transaction is larger (greater than 10K bytes) the fee can be higher.

What is 10k bytes in money terms? BTC 1 / 2 / 5 / 10? And how does one check on Bitcoin-Qt the size (in k bytes) of the transaction to be made?

Thanks
DannyHamilton
Legendary
*
Offline Offline

Activity: 3360
Merit: 4570



View Profile
April 25, 2013, 03:06:20 PM
 #7

Well, to avoid the transaction being considered "low priority" a fee of 0.0005 BTC would do that.  Additionally, if the transaction is larger (greater than 10K bytes) the fee can be higher.
What is 10k bytes in money terms? BTC 1 / 2 / 5 / 10? And how does one check on Bitcoin-Qt the size (in k bytes) of the transaction to be made?

That depends on the quantity and value of the transactions you've received.

When you create a transaction, you spend previously received transactions.

So, if you receive a single transaction valued at 10 BTC, then you can create a transaction that sends 9 BTC and it will use less than 500 bytes.  The transaction will have one input (the previously received 10 BTC transaction) and 2 outputs (one for 9 BTC to the address you are sending to, and the other for 1 BTC in "change" that is sent back into your wallet).

On the other hand, if you receive 100 transactions each valued at 0.1 BTC (you still have a total of 10 BTC in your wallet, but now it is split up into 100 separate 0.1 BTC transactions), then creating a transaction that sends 9 BTC will require more than 10 kilobytes. The transaction will have at least 90 inputs (90 of the previously received 0.1 BTC transactions) and at least one output (assigning the total of 9 BTC of value to the address you are sending to).

There is no way to know how big the transaction will be until after Bitcoin-Qt has chosen the previous transactions that it will be spending.  Then it tells you if a fee is needed and how much that fee will be.

There are some wallets that have "coin-control".  With those wallets, you are able to choose which of the unspent outputs in your wallet you want to use as inputs to the transaction you are creating.  This gives you a bit more control over how many outputs are used and therefore over the size of the transaction.
Loozik
Sr. Member
****
Offline Offline

Activity: 378
Merit: 250


Born to chew bubble gum and kick ass


View Profile
April 26, 2013, 04:41:07 PM
 #8

That depends on the quantity and value of the transactions you've received........... over how many outputs are used and therefore over the size of the transaction.

Thank you for the explanation. Things are much clearer for me now.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!