is my fee ok ?

[zOU]

hello,

I just sent a 37181 (bytes) transaction and the fee was 0.000018846453833947445 BTC per kB (0.00070073BTC)

I've some problem calculating the fee and the transaction size, but that's what was sent....

Does it seem ok ?

[Slark]

If you want to know more about  rules of bitcoin transaction and formula on which transaction fees are based upon, you can see this site: http://bitcoinfees.com/
You will find there prettu much detailed explanation how bitcoin fee works.

Basically size of transaction depends on number inputs and outputs and it is calculated by this formula:

148 * number_of_inputs + 34 * number_of_outputs + 10

[zOU]

Thank you

I found out the number of inputs and output after sending the transaction (unfortnately)

size: 37181 bytes

my fee was 0.0007BTC (which seemed ok at the time)

But it seems it has not been confirmed after a few blocks....

============

in theory:
minrelaytxfee   0.00001 (BTC/kB)

so my Tx being 37kB, my fee should have been 0.00037... but it's nearly twice that ! So shouldn't it have been confirmed quite fast ?

[ralle14]

The transaction might be set on medium priorities even you doubled the transaction fees it could take a few days before it gets confirmed also the recommended fee with that size should be .0037 not .00037.
heres a guide/faq about your problem https://bitcointalk.org/index.php?topic=232979.0

[adamstgBit]

Thank you

I found out the number of inputs and output after sending the transaction (unfortnately)

size: 37181 bytes

my fee was 0.0007BTC (which seemed ok at the time)

But it seems it has not been confirmed after a few blocks....

============

in theory:
minrelaytxfee   0.00001 (BTC/kB)

so my Tx being 37kB, my fee should have been 0.00037... but it's nearly twice that ! So shouldn't it have been confirmed quite fast ?

yes you got lucky i guess, dont feel special it happens often.

thats such a big TX
normally TX are <1KB
how did you manage such a massive TX? lots of tiny inputs? why?

[zOU]

yes you got lucky i guess, dont feel special it happens often.

thats such a big TX
normally TX are <1KB
how did you manage such a massive TX? lots of tiny inputs? why?

251 inputs...

i'm just being stupid and didn't realize it would take all the individual transactions I received from the pool (where I mine) and re-use them.

That's just me not being so familiar with the whole BTC thing
I thought that my client wallet would consolidate the prev transactions in 1/per address.

I had enough BTC in 2 adresses, but one of these had hundreds of transactions....

so it took 251 of my transactions in 2 adresses to get enough BTC to make the payment.....

0.00001 (BTC/kB) x37 = 0.00037
my fee was 0.0007 BTC

[zOU]

ah well, it finally shows 2 confirmations

[Dabs]

It will eventually confirm, but if in case it does not confirm by the end of today, you might want to re-do the transaction with a bigger fee.

*edit* I see it has confirmed.

[franky1]

most people are paying 0.0003 as standard even for low data.

https://bitcoinfees.21.co/
shows 30 sats per byte and knowing ur tx is about 70x the standard size im expecting a higher fee then standard would be acceptable

so

37181byte*30sat=0.01115430btc for tx fee

seems in your OP you decided less than 2sat per byte (1885 sat per kb), so expect it to have taken about an hour+ to confirm

edit: seems it did take over an hour
next time try a 0.012 fee (by the way thats $5) and now you know why letting blockstreamers say everything is working fantastically, is utter crap if it takes $5 for you to get priority

[Boosterious]

Thank you

I found out the number of inputs and output after sending the transaction (unfortnately)

size: 37181 bytes

my fee was 0.0007BTC (which seemed ok at the time)

But it seems it has not been confirmed after a few blocks....

============

in theory:
minrelaytxfee   0.00001 (BTC/kB)

so my Tx being 37kB, my fee should have been 0.00037... but it's nearly twice that ! So shouldn't it have been confirmed quite fast ?

yes you got lucky i guess, dont feel special it happens often.

thats such a big TX
normally TX are <1KB
how did you manage such a massive TX? lots of tiny inputs? why?

you all look like have good knowledge about bitcoin transaction fee,but until now i dont get any explaination about bigger fee than amount transacted,som couple days ago i see someone post about that case,and just get explain about "bitpool mistake"

[calkob]

Did you send it from core ?

[18xk5oT2rLrAc24SL96XT14BX]

It will eventually confirm, but if in case it does not confirm by the end of today, you might want to re-do the transaction with a bigger fee.

*edit* I see it has confirmed.

i think you are right It will eventually confirm, but if in case it does not confirm by the end of today, you might want to re-do the transaction with a bigger fee.

[noormcs5]

yes you got lucky i guess, dont feel special it happens often.

thats such a big TX
normally TX are <1KB
how did you manage such a massive TX? lots of tiny inputs? why?

251 inputs...

i'm just being stupid and didn't realize it would take all the individual transactions I received from the pool (where I mine) and re-use them.

That's just me not being so familiar with the whole BTC thing
I thought that my client wallet would consolidate the prev transactions in 1/per address.

I had enough BTC in 2 adresses, but one of these had hundreds of transactions....

so it took 251 of my transactions in 2 adresses to get enough BTC to make the payment.....

0.00001 (BTC/kB) x37 = 0.00037
my fee was 0.0007 BTC

I think there is something abnormal in the Fee.