<p>what brought my attention <a href="https://blockchain.info/tx/fc1731fbf666284585a253f390e8868e0307b667cd5bc37cf2ef0f1a578c1e30" rel="nofollow noreferrer">this transaction</a> size</p>

<p>this transaction contains 2 SegWit inputs which mean it should be compressed and five outputs.</p>

<p>As we know, each compressed input size is ≈ 148 bytes, and each output is 34.</p>

<p>So transactions size should be (148 * 2) + (5 * 34) + 10 = 476</p>

<p>But actual transaction size is 516 Byte.</p>

<hr>

<p>is it a multi-signature transaction? if so is all other transaction which has one signature has a size of 148 Byte? </p>

<blockquote>
  <p>I apologize for not being word-perfect in English</p>
</blockquote>

CC BY-SA 3.0
2018-01-03T11:04:17.180Z
Why did you delete the question?
meshcollider
CC BY-SA 3.0
2018-01-03T11:48:27.887Z
Because I have to read more about input scripts. I've seen that some input scripts are longer than the usual ones. So I guess I miss something.
Tailer
CC BY-SA 3.0
2018-01-03T11:55:59.153Z
I've restored it in case you got something good to share.
Tailer
<transaction-fees>
how does this transaction size calculated
Tailer
# how does this transaction size calculated

(Asked by: username_0 on 2018-01-03)

what brought my attention [this transaction](https://blockchain.info/tx/fc1731fbf666284585a253f390e8868e0307b667cd5bc37cf2ef0f1a578c1e30) size

this transaction contains 2 SegWit inputs which mean it should be compressed and five outputs.

As we know, each compressed input size is ≈ 148 bytes, and each output is 34.

So transactions size should be (148 \* 2) + (5 \* 34) + 10 = 476

But actual transaction size is 516 Byte.

---

is it a multi-signature transaction? if so is all other transaction which has one signature has a size of 148 Byte?

> I apologize for not being word-perfect in English

**Tags:** transaction-fees

> **Comments:**
> **username_1**: Why did you delete the question?  
> **username_0**: Because I have to read more about input scripts. I've seen that some input scripts are longer than the usual ones. So I guess I miss something.  
> **username_0**: I've restored it in case you got something good to share.  

---

## 0 answers

