List Logs By Transaction Hash

This endpoint allows customers to retrieve transaction logs associated with a specific blockchain transaction. In blockchain technology, transaction logs are essential for auditing, debugging, and monitoring the execution of smart contracts and transactions. This endpoint provides a convenient and efficient way to access these logs.

List of Results - This endpoint returns multiple objects which means pagination is applicable. GET /blockchain-data/{blockchain}/{network}/transactions/{transactionHash}/logs

Path Parameters

  • Required
    blockchain string

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

    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", "goerli" are test networks.

    Example : sepolia
    Possible Values : mainnet sepolia
  • Required
    transactionHash string

    Represents the unique identifier of a transaction, i.e. it could be transactionId in UTXO-based protocols like Bitcoin, and transaction hash in Ethereum blockchain.

    Example : 0x77041a2573f9edb5c443172acf369dc218102b006624bf0f276f32637807550f

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.

    Example : yourExampleString

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 : 2023-04-25
  • 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 : yourExampleString
  • Required
    data object
    • Required
      limit integer

      Defines how many items should be returned in the response per page basis.

      Example : 50
    • Required
      offset integer

      The starting index of the response items, i.e. where the response should start listing the returned items.

      Example : 0
    • Required
      total integer

      Defines the total number of items returned in the response.

      Example : 100
    • Required
      items array
      Example : Array ( )
      • Required
        address string

        Represents the address from which this log is generated.

        Example : 0xD04E772BC0d591fBD288f2E2a86aFA3D3CB647F8
      • Required
        data string

        Representation of the 32 byte non-indexed argument of the log

        Example : 0x0000000000000000000000000000000000000000000018aa053302d4ad9e2c9c
      • Required
        isRemoved boolean

        Representation of whether the event was removed

        Example : True
      • Optional
        name string

        Representation of the name of the text event signature

        Example : Transfer (index_topic_1 address from, index_topic_2 address to, uint256 value)
      • Required
        topics array

        Representation of the topics associated with the event

        Example : 0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef

Credits Cost : 500 Credits For 1 Result(s)

Try it out

Request Example

GET
https://rest.cryptoapis.io/blockchain-data/ethereum/sepolia/transactions/0x77041a2573f9edb5c443172acf369dc218102b006624bf0f276f32637807550f/logs?context=yourExampleString
Headers
Content-Type: application/json
X-API-Key: my-api-key

Response Example

{
    "apiVersion": "2023-04-25",
    "requestId": "601c1710034ed6d407996b30",
    "context": "yourExampleString",
    "data": {
        "limit": 50,
        "offset": 0,
        "total": 100,
        "items": [
            {
                "address": "0xD04E772BC0d591fBD288f2E2a86aFA3D3CB647F8",
                "data": "0x0000000000000000000000000000000000000000000018aa053302d4ad9e2c9c",
                "isRemoved": true,
                "name": "Transfer (index_topic_1 address from, index_topic_2 address to, uint256 value)",
                "topics": [
                    "0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef"
                ]
            }
        ]
    }
}