# \`global LatestTimestamp\` is 0 in when debugging from dryrun txn

**URL:** <https://forum.algorand.co/t/global-latesttimestamp-is-0-in-when-debugging-from-dryrun-txn/6117>\
**Category:** General\
**Tags:** teal\
**Created:** [February 25, 2022, 2:39am UTC](https://forum.algorand.co/t/global-latesttimestamp-is-0-in-when-debugging-from-dryrun-txn/6117 "2022-02-25T02:39:05Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![casper](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/casper/32/1612_2.png) [@casper](https://forum.algorand.co/u/casper)\
**Post date:** [February 25, 2022, 2:39am UTC](https://forum.algorand.co/t/global-latesttimestamp-is-0-in-when-debugging-from-dryrun-txn/6117/1 "2022-02-25T02:39:05Z")

</div>

I’m debugging a contract and the `global LatestTimestamp` instruction is putting 0 on the stack. Does anyone know a reason for this? I’m running against a private node

---

_[View the full topic](https://forum.algorand.co/t/global-latesttimestamp-is-0-in-when-debugging-from-dryrun-txn/6117)._