TRON - Missing or Incorrect Timestamps in Transactions

TRON behaves differently from other chains when it comes to transaction timestamps.

This article outlines how TRON handles timestamps, why some transactions return no timestamp, and how to correctly retrieve authoritative timing information when interacting with Tatum's TRON APIs.

Background

Tron Transactions may not include a transaction-level timestamp and when they do, they can be incorrect. Blocks always include a timestamp, and TRON block explorers (including Tronscan) display block time, not transaction time.

However, many transactions, especially those created manually or programmatically, can and will omit timestamp fields because TRON does not require them. This is a confirmed, upstream protocol behavior

As a result, Tatum's endpoint /v4/data/blockchains/transaction?chain=tron-### may return transactions with missing or incorrect timestamp.

🚧

Attention

This behaviour is documented in the TRON Core implementation: Issue #3845 – Some transactions have no timestamp

How to Retrieve Transaction Timestamps on TRON

Since transactions may not contain timestamps, you must rely on block timestamps.

Step_1: Fetch the transaction

• DATA API: Get transaction by hash

curl --request GET \
     --url 'https://api.tatum.io/v4/data/blockchains/transaction?chain=tron-mainnet&hash=#####' \
     --header 'accept: application/json' \
     --header 'x-api-key: {YOUR_API_KEY}'
     //Response:
     //[...]   
     "blockNumber": BBBBB,
     //[...]

Extract blockNumber.

Step_2: Fetch the block containing the transaction

• DATA API: Get block by hash or height

curl --request GET \
     --url 'https://api.tatum.io/v4/data/blockchains/block?chain=tron-mainnet&hashOrHeight=BBBBB' \
     --header 'accept: application/json' \
     --header 'x-api-key: {YOUR_API_KEY}'
     //Response:
     //[...]
     "timestamp": 1773912534000,
     //[...]

This timestamp is the canonical time for the transaction.

Key Takeaways

• Incorrect or missing timestamp field in TRON transactions is an expected behaviour.
• TRON does not mandate transaction timestamps.
• Block timestamp is the correct source of truth.