<p>If you are trying to minimize your expenses from sending transaction, consider this bit from <a href="https://en.bitcoin.it/wiki/Transaction_fees" rel="nofollow">https://en.bitcoin.it/wiki/Transaction_fees</a></p>

<p>Sending</p>

<p>A transaction may be safely sent without fees if these conditions are met:</p>

<p>It is smaller than 1,000 bytes.</p>

<p>All outputs are 0.01 BTC or larger.</p>

<p>Its priority is large enough (see the Technical Info section below)</p>

<p>Otherwise, the reference implementation will round up the transaction size to the next thousand bytes and add a fee of 0.1 mBTC (0.0001 BTC) per thousand bytes[1]. As an example, a fee of 0.1 mBTC (0.0001 BTC) would be added to a 746 byte transaction, and a fee of 0.2 mBTC (0.0002 BTC) would be added to a 1001 byte transaction. Users may increase the default 0.0001 BTC/kB fee setting, but cannot control transaction fees for each transaction. </p>

<p>Bitcoin-Qt does prompt the user to accept the fee before the transaction is sent (they may cancel the transaction if they are not willing to pay the fee).</p>

<p>Note that a typical transaction is 500 bytes, so the typical transaction fee for low-priority transactions is 0.1 mBTC (0.0001 BTC), regardless of the number of bitcoins sent.</p>

CC BY-SA 3.0
2014-02-09T19:49:43.510Z
2014-02-09T19:49:43.510Z
Mark
<p>It's not about size, it's about fee. If you can have a high enough fee to make a massively sized transaction be incentived to miners, your good. See transaction priority for what I mean.</p>

CC BY-SA 3.0
2014-01-10T14:24:37.413Z
I understand what you are saying about fees... Perhaps I'm over thinking it. My assumption is that large transactions might have a harder time getting included in a block because the block may be filled with a number of smaller transactions. Thus, there should be an equilibrium point where over that point (this is the point I'm trying to ascertain) it becomes harder to include large transaction in a block
user789235
CC BY-SA 3.0
2014-01-10T08:02:56.053Z
2014-01-10T08:02:56.053Z
John T
<p>I know the maximum transaction size for a BLOCK is 250,000 bytes. My question is a little different.</p>

<p>What is a recommended transaction size for best selection of the transaction by pools? For example say I have 500,000 bytes of transaction to send over the network. How should I chunk those transactions? 50,000 byte transactions? 10,000 byte transactions?</p>

<transactions>
Recommended Transaction Size
user789235
# Recommended Transaction Size

(Asked by: username_0 on 2014-01-09)

I know the maximum transaction size for a BLOCK is 250,000 bytes. My question is a little different.

What is a recommended transaction size for best selection of the transaction by pools? For example say I have 500,000 bytes of transaction to send over the network. How should I chunk those transactions? 50,000 byte transactions? 10,000 byte transactions?

**Tags:** transactions


---

## 2 answers

### Answer by username_1 on 2014-02-09. Score: 1

If you are trying to minimize your expenses from sending transaction, consider this bit from <https://en.bitcoin.it/wiki/Transaction_fees>

Sending

A transaction may be safely sent without fees if these conditions are met:

It is smaller than 1,000 bytes.

All outputs are 0.01 BTC or larger.

Its priority is large enough (see the Technical Info section below)

Otherwise, the reference implementation will round up the transaction size to the next thousand bytes and add a fee of 0.1 mBTC (0.0001 BTC) per thousand bytes[1]. As an example, a fee of 0.1 mBTC (0.0001 BTC) would be added to a 746 byte transaction, and a fee of 0.2 mBTC (0.0002 BTC) would be added to a 1001 byte transaction. Users may increase the default 0.0001 BTC/kB fee setting, but cannot control transaction fees for each transaction.

Bitcoin-Qt does prompt the user to accept the fee before the transaction is sent (they may cancel the transaction if they are not willing to pay the fee).

Note that a typical transaction is 500 bytes, so the typical transaction fee for low-priority transactions is 0.1 mBTC (0.0001 BTC), regardless of the number of bitcoins sent.


---

### Answer by username_2 on 2014-01-10. Score: 1

It's not about size, it's about fee. If you can have a high enough fee to make a massively sized transaction be incentived to miners, your good. See transaction priority for what I mean.

> **Comments:**
> **username_0**: I understand what you are saying about fees... Perhaps I'm over thinking it. My assumption is that large transactions might have a harder time getting included in a block because the block may be filled with a number of smaller transactions. Thus, there should be an equilibrium point where over that point (this is the point I'm trying to ascertain) it becomes harder to include large transaction in a block  

---

