Skip to main content
GET
/
95e61622bf6a8af293978377718e3b77
/
wallet
/
gettransactionlistfrompending
wallet/gettransactionlistfrompending
curl --request GET \
  --url https://tron-mainnet.core.chainstack.com/95e61622bf6a8af293978377718e3b77/wallet/gettransactionlistfrompending
{
  "transactions": [
    {
      "txID": "f34f1c799700a9d83b67fdcadd7be697010a8dbbcd520de4ac46a648e3e7ae3d",
      "raw_data": {
        "contract": [
          {
            "type": "TransferContract",
            "parameter": {}
          }
        ],
        "ref_block_bytes": "6f80",
        "ref_block_hash": "1c9c4b8c43c5e0b1",
        "expiration": 1704067260000,
        "timestamp": 1704067200000,
        "fee_limit": 100000000
      },
      "signature": [
        "<string>"
      ],
      "ret": [
        {
          "contractRet": "SUCCESS"
        }
      ]
    }
  ]
}
TRON API method that retrieves a list of all pending transactions currently in the mempool. This allows applications to monitor unconfirmed transactions awaiting inclusion in a block.
Get you own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.

​
Parameters

This method requires no parameters. It returns all pending transactions in the current mempool.

​
Response

  • transactions — array of pending transaction objects, each containing:
    • txID — unique transaction identifier hash
    • raw_data — raw transaction data including:
      • contract — array with transaction contract details
      • ref_block_bytes — reference block bytes for validation
      • ref_block_hash — hash of the reference block
      • expiration — transaction expiration timestamp
      • timestamp — transaction creation timestamp
      • fee_limit — maximum fee allowed for this transaction
    • signature — array of transaction signatures
    • ret — transaction result information (if available)

​
Use case

The wallet/gettransactionlistfrompending method is used for:
  • Monitoring pending transactions in real-time for transaction status tracking.
  • Building transaction pool analytics and network congestion monitoring tools.
  • Implementing custom mempool explorers and pending transaction dashboards.
  • Analyzing transaction patterns and fee structures before confirmation.
  • Creating alerts for specific pending transactions or transaction types.
The pending transaction pool is dynamic and constantly changing as transactions get confirmed or dropped. The response represents a snapshot at the time of the request and may vary between consecutive calls.

Response

200 - application/json

List of all pending transactions

​
transactions
object[]

Array of pending transaction objects