Delayed Transactions

Delayed transactions use an extended 'expiration' parameter (> 1 hour). Transatron process such transactions differently. It will keep them in the internal storage until the near expiration time, and broadcast to the Tron node at the last movement. This section provides endpoints to check pending delayed transactions and trigger immediate execution with Flush.

📄️ About Delayed Transactions

Delayed transactions are created by extending the expiration parameter beyond the standard 1-hour window. Instead of broadcasting immediately, Transatron stores these transactions in an internal buffer and processes them in batches closer to the expiration time. This batching reduces overall resource consumption and fees.

📄️ GET Pending Transactions

This call only returns data when Delayed transactions are enabled for the API key

📄️ POST Flush Pending Transactions

Flush only applies when Delayed transactions are enabled for the API key (the default).