If I undestend the your question, you referer to the lockTime inside the transaction and not the block timestamp.
The lockTime is a int value, and this value rappresent "When the transaction can be unlockd to an inputs" and not "When the transaction was published"
Lock time: Defines the first instant in which the transaction is considered valid and can be transmitted on the Bitcoin network, represented by an integer value between 0 and 500 million, assuming different meanings based on the value assigned, that is:
- Lock time = 0: the transaction is propagated and executed at the instant of
- 0 < LockTime <= 500: the value is interpreted as a block height, ie the
transaction will be valid only after the block with height
equal to the lock time value has been published.
- Lock time> 500 million: the value is interpreted as a unix timestamp and
therefore the transaction will be valid only after the
date represented by the lock time value.
If you mean if the transaction has a timestamp, the answer is two:
Within the structure the transaction does not have a timestamp, but
rather a lock time.
The transaction could have an insertion moment in the block, which
depends on the block, because it is he who holds the timestamp as a
A real use case:
My transaction has a block timestamp equal to 8/23/2019, 2:08:43 PM GMT + 2, this represents the time in which the miner started the cryptographic challenge, and it is the instant in which the miner has also taken into consideration my transaction including it in the block.
My transaction has a lockTime of 0 because it is an immediate execution transaction.
No one excuses that my transaction before the block was published was ALSO inside some other block with a slightly different timestamp
If you want have turn a detailed explanation of what and how a transaction works, I recommend this reading on bitcoin book