Jump to
Ctrl
+
/

List Logs By Transaction Hash

GET
/blockchain-data/{blockchain}/{network}/transactions/{transactionHash}/logs

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.

Path Parameters

blockchain string Required

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

network string Required

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.

transactionHash string Required

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.

Query Parameters

context string Optional

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

apiVersion string Required

Specifies the version of the API that incorporates this endpoint.

2023-04-25
requestId string Required

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

601c1710034ed6d407996b30
context string Optional

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.

yourExampleString
data object Required
limit integer Required

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

50
offset integer Required

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

0
total integer Required

Defines the total number of items returned in the response.

100
items array Items (object) Required
address string Required

Represents the address from which this log is generated.

0xD04E772BC0d591fBD288f2E2a86aFA3D3CB647F8
data string Required

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

0x0000000000000000000000000000000000000000000018aa053302d4ad9e2c9c
isRemoved boolean Required

Representation of whether the event was removed

true
name string Optional

Representation of the name of the text event signature

Transfer (index_topic_1 address from, index_topic_2 address to, uint256 value)
topics array Items (string) Required

Credits Cost : 500 Credits for 1 Results

Was this page helpful?
Yes
No
Powered by
Language
URL

{
    "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"
                ]
            }
        ]
    }
}