# Indexer Inner Transaction Design

**URL:** <https://forum.algorand.co/t/indexer-inner-transaction-design/7906>\
**Category:** Uncategorized\
**Created:** [September 27, 2022, 5:59pm UTC](https://forum.algorand.co/t/indexer-inner-transaction-design/7906 "2022-09-27T17:59:48Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![will](https://avatars.discourse-cdn.com/v4/letter/w/90ced4/32.png) [@will](https://forum.algorand.co/u/will)\
**Post date:** [September 29, 2022, 4:41pm UTC](https://forum.algorand.co/t/indexer-inner-transaction-design/7906/4 "2022-09-29T16:41:00Z")

</div>

The TxnCounter was not part of the consensus protocol when we launched, which is why you don’t see it until round 3317192 on mainnet. In addition, there were some empty blocks before it. The value would have been omitted until the first transaction after the protocol upgrade.

It looks like there was one transaction on round 3317192, which is why you see the value is 1. There were no transactions on round 3317193, so it remained 1. There was one transaction on round 3317194, so it was incremented to 2. Etc.

---

_[View the full topic](https://forum.algorand.co/t/indexer-inner-transaction-design/7906)._