Through this endpoint customers can list internal transactions by the address
attribute.
Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - "mainnet" is the live network with actual data while networks like "testnet", "sepolia" are test networks.
String identifier of the address document represented in CryptoAPIs
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context
is specified by the user.
Specifies the version of the API that incorporates this endpoint.
Defines the ID of the request. The requestId
is generated by Crypto APIs and it's unique for every request.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context
is specified by the user.
Defines how many items should be returned in the response per page basis.
Defines the id of the previous listed record id from which the current list should start from.
Defines whether or not there are more elements available after this set.
Defines the id of the next page which the next list should start from.
Defines what the sorting order is either ascending or descending.
Defines the specific hash of the parent transaction.
Represents the hash of the block where this transaction was mined/confirmed for first time. The hash is defined as a cryptographic digital fingerprint made by hashing the block header twice through the SHA256 algorithm.
Numeric representation of the block height
String representation of internal transaction type trace address
String representation of internal transaction type
String representation of the internal transaction recipient
String representation of the internal transaction sender
Numeric representation of the timestamp in seconds since epoch
String representation of the amount that was transacted
String representation of the value unit
API Key
{
"apiVersion": "2024-12-12",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"data": {
"limit": 50,
"startingAfter": "5ca21f92cf5431000105d1a7",
"hasMore": true,
"nextStartingAfter": "5ca21f92cf5431000105d1a7",
"sortingOrder": "ascending",
"items": [
{
"transactionHash": "0x5d4ea0471b70de09fa3d6a4bc32f703ec44483bffa4d6169fa0a36c6a1dc108a",
"minedInBlock": {
"hash": "0x85ce0aa9628726c60db14526be8a2b823084b1f4c3dcccdc10b0235f23a49e66",
"height": 69567970
},
"operationId": "call_0_0",
"operationType": "CALL",
"recipient": "TRpc3xTyUH7vX45XptZyHEBNoUqDteGoRm",
"sender": "TJ5usJLLwjwn7Pw3TPbdzreG7dvgKzfQ5y",
"timestamp": 1739356303,
"value": {
"amount": "39",
"unit": "TRX"
}
}
]
}
}