Topic: Transaction fee for the network to confirm a tx w/1 input and many outputs (Read 332 times)
April 29, 2013, 04:52:51 PM
Awesome, thank you!
April 29, 2013, 12:50:09 PM
You'll need to pay a fee per kilobyte ( can't remember if it's 0.0001 BTC or 0.0005 BTC).
The overhead in the structure of the transaction itself is between 6 and 12 bytes. Then the one input will be somewhere around 180 bytes (give or take a couple bytes).
Each output will be 34 bytes.
So, figure worst case 191 + (34 * output_quantity) bytes.
Note that there is a limit to the maximum size a transaction can be and still be accepted/relayed by peers.
The overhead in the structure of the transaction itself is between 6 and 12 bytes. Then the one input will be somewhere around 180 bytes (give or take a couple bytes).
Each output will be 34 bytes.
So, figure worst case 191 + (34 * output_quantity) bytes.
Note that there is a limit to the maximum size a transaction can be and still be accepted/relayed by peers.
April 29, 2013, 06:28:22 AM
I'm considering a site which would require taking a single transaction as input, and sending it to potentially hundreds or thousands of separate addresses in a single transaction.
Can someone help me figure out the amount, in tx fees, which would be needed for the network to confirm the transaction in a reasonable amount of time?
Can someone help me figure out the amount, in tx fees, which would be needed for the network to confirm the transaction in a reasonable amount of time?
Jump to: