Get Internal Transaction by Transaction Hash and Operation Id

Through this endpoint customers can obtain detailed information about a specific Internal Transaction by using the attributes transactionHash (the parent transaction's Hash) and operationId (type trace address).

An internal transaction is the result of a smart contract being triggered by an EOA or a subsequent contract call.

GET /blockchain-data/{blockchain}/{network}/transactions/{transactionHash}/internal/{operationId}

Path Parameters

  • Required
    blockchain string

    Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.

    Default : ethereum
    Example : ethereum
    Possible Values : ethereum
  • Required
    network 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", "rinkeby" are test networks.

    Default : ropsten
    Example : mainnet
    Possible Values : mainnet
  • Required
    operationId string

    Represents the unique internal transaction ID in regards to the parent transaction (type trace address).

    Example : call_4
  • Required
    transactionHash string

    String identifier of the parent transaction of the internal transaction represented in CryptoAPIs.

    Example : 0x92bb77e16444e0417c8b50dfab68e89c7ad27d4140a766c3bbd4d0ac195f12fc

Query parameters

  • Optional
    context 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.

Response schema

200 400 401 402 403 404 409 415 422 429 500
HTTP Status Code: 200
Content-Type: application/json

The request has been successful.

  • Object :

  • Required
    apiVersion string

    Specifies the version of the API that incorporates this endpoint.

    Example : 2.0
  • Required
    requestId string

    Defines the ID of the request. The requestId is generated by Crypto APIs and it's unique for every request.

    Example : 601c1710034ed6d407996b30
  • Optional
    context 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 : You can add any text here
  • Required
    data object
    • Required
      item object
      • Required
        amount string

        Defines the specific amount of the transaction.

        Example : 0.000479716904346335
      • Required
        blockHash 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 : 0x61262bd96d7cf50884e8ce61a5cf978d748417d28d3d76aea889346f050a2fbb
      • Required
        blockHeight 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 : 12561779
      • Required
        operationType string

        Defines the specific type of the operation.

        Example : CALL
      • Required
        parentHash string

        Defines the specific hash of the parent transaction.

        Example : 0x92bb77e16444e0417c8b50dfab68e89c7ad27d4140a766c3bbd4d0ac195f12fc
      • Required
        recipient string

        Represents the recipient address with the respective amount.

        Example : 0xef7cfdee2f0ef5ae5e0c60098c8838fa7822754e
      • Required
        sender string

        Represents the sender address with the respective amount.

        Example : 0x7a250d5630b4cf539739df2c5dacb4c659f2488d
      • Required
        timestamp 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 : 1622726449
Try it out

Request Example

GET
https://rest.cryptoapis.io/v2/blockchain-data/ethereum/mainnet/transactions/0x92bb77e16444e0417c8b50dfab68e89c7ad27d4140a766c3bbd4d0ac195f12fc/internal/call_4
Headers
Host: https://rest.cryptoapis.io/v2
Content-Type: application/json
X-API-Key: my-api-key

Response Example

{
    "apiVersion": "2.0",
    "requestId": "601c1710034ed6d407996b30",
    "context": "You can add any text here",
    "data": {
        "item": {
            "amount": "0.000479716904346335",
            "blockHash": "0x61262bd96d7cf50884e8ce61a5cf978d748417d28d3d76aea889346f050a2fbb",
            "blockHeight": 12561779,
            "operationType": "CALL",
            "parentHash": "0x92bb77e16444e0417c8b50dfab68e89c7ad27d4140a766c3bbd4d0ac195f12fc",
            "recipient": "0xef7cfdee2f0ef5ae5e0c60098c8838fa7822754e",
            "sender": "0x7a250d5630b4cf539739df2c5dacb4c659f2488d",
            "timestamp": 1622726449
        }
    }
}