20000Bytes transaction wtf???

[EvenMatt]

hello
i just sent money from my blockchain.info wallet
why is the transaction so heavy 20000bytes !!! i paid 13$ fees for that and it already takes very long to be confirmed still 0 confimation after 80mintues!
will it ever go through? is my money lost?
what happened?
Help ;(

[1715546898]

1715546898

[1715546898]

1715546898

[1715546898]

1715546898

[unholycactus]

Can you link the transaction?
You probably have a lot of inputs, probably due to the fact that you were doing a lot of micro transactions and sending them all out at once.
I'm curious to see how you reached 20k though.

[EvenMatt]

Can you link the transaction?
You probably have a lot of inputs, probably due to the fact that you were doing a lot of micro transactions and sending them all out at once.
I'm curious to see how you reached 20k though.

sent

[EvenMatt]

still need help guys

[pooya87]

you paid a small amount of fee!
according to http://bitcoinfees.21.co/ you needed to pay 110 satoshi per byte and if you are saying the size correctly (20,000 bytes) it means you should have paid 0.022BTC fee for it which is ~$20
what you paid ($13) is ~0.014BTC

it will take a longer time to confirm mostly because there are 20K unconfrimed transactions right now (https://blockchain.info/unconfirmed-transactions)

you should wait but also try using this: https://www.viabtc.com/tools/txaccelerator/

I'm curious to see how you reached 20k though.

here is an example for your curiosity 52135 (bytes)
https://blockchain.info/tx/ef492f5dd516f51061a77bc148b8925e74557b1f31a42ca51098f26b82c23fb0

[shorena]

-snip-
here is an example for your curiosity 52135 (bytes)
https://blockchain.info/tx/ef492f5dd516f51061a77bc148b8925e74557b1f31a42ca51098f26b82c23fb0

I think with "advanced view" its more clear.

-> https://blockchain.info/tx/ef492f5dd516f51061a77bc148b8925e74557b1f31a42ca51098f26b82c23fb0?show_adv=true

Every input (shown on the left) needs ~148 (or 180[1]) bytes and this TX has 290 inputs. 290*180 = 52 200 ~= 52 135.

[1] for uncompressed pubkeys as in this example.

[Lauda]

Every input (shown on the left) needs ~148 (or 180[1]) bytes and this TX has 290 inputs. 290*180 = 52 200 ~= 52 135.

It may be useful to put the full 'calculation' for the TX size in here (unless something has changed):

in*180 + out*34 + 10 plus or minus 'in'

https://bitcoin.stackexchange.com/questions/1195/how-to-calculate-transaction-size-before-sending
Generally I recommend that people combine outputs whenever they can. This is also beneficial for the network as it reduces the UTXO set.

[pooya87]

~
I think with "advanced view" its more clear.

well, i assumed a "curious" person would investigate further

the interesting thing about that transaction for me was this part "0xfd2201" which translates to "290" inputs based on how ComactSize is defined.