List Internal Transaction Details by Transaction Hash
Through this endpoint customers can list internal transactions along with their details by a specific attribute transactionHash
, which is the parent transaction's Hash.
An internal transaction is the result of a smart contract being triggered by an EOA or a subsequent contract call.
Path Parameters
-
Requiredblockchain string
Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
-
Requirednetwork string
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", "ropsten" are test networks.
-
RequiredtransactionHash string
String identifier of the parent transaction of the internal transaction represented in CryptoAPIs.
Query parameters
-
Optionalcontext string
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. -
Optionallimit integer
Defines how many items should be returned in the response per page basis.
-
Optionaloffset integer
The starting index of the response items, i.e. where the response should start listing the returned items.
Response schema
Content-Type: application/json
The request has been sussessful.
Object :
-
RequiredapiVersion string
Specifies the version of the API that incorporates this endpoint.
Example : 2021-03-20 -
RequiredrequestId string
Defines the ID of the request. The
requestId
is generated by Crypto APIs and it's unique for every request.Example : 601c1710034ed6d407996b30 -
Optionalcontext string
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.Example : yourExampleString -
Requireddata object
-
Requiredlimit integer
Defines how many items should be returned in the response per page basis.
Example : 50 -
Requiredoffset integer
The starting index of the response items, i.e. where the response should start listing the returned items.
Example : 0 -
Requiredtotal integer
Defines the total number of items returned in the response.
Example : 100 -
Requireditems arrayExample : Array ( )
-
Requiredamount string
Defines the specific amount of the transaction.
Example : 0.089286906469667626 -
RequiredblockHash string
Represents the hash of the block, which is its unique identifier. It represents a cryptographic digital fingerprint made by hashing the block header twice through the SHA256 algorithm.
Example : 0x47245a445acd6c7a328d033313ea621fbc0642aaf913790e9d558c1c208625f0 -
RequiredblockHeight integer
Represents the number of blocks in the blockchain preceding this specific block. Block numbers have no gaps. A blockchain usually starts with block 0 called the "Genesis block".
Example : 12561919 -
RequiredoperationID string
Represents the unique internal transaction ID in regards to the parent transaction (type trace address).
Example : call_1 -
RequiredoperationType string
Defines the call type of the internal transaction.
Example : CALL -
RequiredparentHash string
Defines the specific hash of the parent transaction.
Example : 0x5d4ea0471b70de09fa3d6a4bc32f703ec44483bffa4d6169fa0a36c6a1dc108a -
Requiredrecipient string
Represents the recipient address with the respective amount.
Example : 0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2 -
Requiredsender string
Represents the sender address with the respective amount.
Example : 0x7a250d5630b4cf539739df2c5dacb4c659f2488d -
Requiredtimestamp integer
Defines the exact date/time in Unix Timestamp when this transaction was mined, confirmed or first seen in Mempool, if it is unconfirmed.
Example : 1622728329
-
-