Details of the Object table and JSON output of list confirmed crypto transactions by address API made by Crypto APIs
Today, I will clarify the object table and JSON output of the Crypto APIs list confirmed crypto transactions by address API. This API allows users to retrieve a list of confirmed cryptocurrency transactions by address. The object table and JSON output provide a structured way to access and organize this data. I will explain the specific contents and format of the object table and JSON output for this API.
Object and Description of API Output
| Objects | Description |
| apiVersion | Specifies the version of the API that incorporates this endpoint. |
| requestId | Defines the ID of the request. The requestId is generated by Crypto APIs and it's unique for every request. |
| context | 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. |
| data | |
| limit | Defines how many items should be returned in the response per page basis. |
| offset | The starting index of the response items, i.e. where the response should start listing the returned items. |
| total | Defines the total number of items returned in the response. |
| items | |
| transactionId | 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. |
| index | Represents the index position of the transaction in the block. |
| minedInBlockHash | 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. |
| minedInBlockHeight | Represents the height of the block where this transaction was mined/confirmed for first time. The height is defined as the number of blocks in the blockchain preceding this specific block. |
| recipients | Represents a list of recipient addresses with the respective amounts. In account-based protocols like Ethereum there is only one address in this list. |
| address | The address which receives this transaction. In UTXO-based protocols like Bitcoin there could be several senders while in account-based protocols like Ethereum there is always only one recipient. |
| amount | Represents the amount received to this address. |
| senders | Represents a list of sender addresses with the respective amounts. In account-based protocols like Ethereum there is only one address in this list. |
| address | Represents the address which sends this transaction. In UTXO-based protocols like Bitcoin there could be several senders while in account-based protocols like Ethereum there is always only one sender. |
| amount | Represents the total amount sent by this address including the fee. |
| timestamp | Defines the exact date/time in Unix Timestamp when this transaction was mined, confirmed or first seen in Mempool, if it is unconfirmed. |
| transactionHash | Represents the same as transactionId for account-based protocols like Ethereum, while it could be different in UTXO-based protocols like Bitcoin. E.g., in UTXO-based protocols hash is different from transactionId for SegWit transactions. |
| blockHash | Represents the same as minedInBlockHash for account-based protocols like Ethereum, while it could be different in UTXO-based protocols like Bitcoin. |
| blockHeight | Represents the same as minedInBlockHeight for account-based protocols like Ethereum, while it could be different in UTXO-based protocols like Bitcoin. |
| totalInputAmount | Represents the total amount received to all the inputs. |
| totalOutputAmount | Represents the total amount sent from all the outputs. |
| fees | Represents the transaction fees. |
| inputs | Represents a list of inputs with the respective amounts. |
| outputs | Represents a list of outputs with the respective amounts. |
| confirmations | Represents the number of confirmations this transaction has. |
| isConfirmed | Represents whether the transaction is confirmed or not. |
| isCoinbase | Represents whether the transaction is coinbase or not. |
The information in the table is useful because it provides a detailed description of the various objects that are returned by the Crypto APIs list confirmed crypto transactions by address API. These objects contain important information about the transactions, such as the unique identifier, the sender and recipient addresses, the amounts involved, the timestamp of the transaction, and the number of confirmations. This information is essential for understanding and working with the data returned by the API, as it allows developers to access and analyze the specific details of each transaction. Additionally, the table provides a clear and organized overview of the available objects, making it easier for developers to understand and navigate the data.
JSON Output
This JSON output represents the response from a Crypto APIs list confirmed crypto transactions by address API. The response includes a top-level object called "data", which contains several properties that provide information about the transactions. The "limit" property specifies how many items should be returned in the response per page basis, while the "offset" property defines the starting index of the response items. The "total" property indicates the total number of items returned in the response. The "items" property is an array of objects, each of which represents a transaction. Each transaction object contains several properties, such as the "transactionId", which is the unique identifier of the transaction, and the "index", which represents the position of the transaction in the block. The "minedInBlockHash" and "minedInBlockHeight" properties provide information about the block where the transaction was mined, while the "recipients" and "senders" properties list the addresses and amounts involved in the transaction. The "timestamp" property indicates the date and time when the transaction was mined, and the "transactionHash" property is the hash of the transaction. The "fee" property contains information about the transaction fees, and the "blockchainSpecific" property includes various details about the transaction that are specific to the blockchain.
{
"apiVersion": "2021-03-20",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"data": {
"limit": 50,
"offset": 0,
"total": 100,
"items": [
{
"transactionId": "4b66461bf88b61e1e4326356534c135129defb504c7acb2fd6c92697d79eb250",
"index": 1,
"minedInBlockHash": "00000000407f119ecb74b44229228910400aaeb9f4e3b9869955b85a53e9b7db",
"minedInBlockHeight": 1903849,
"recipients": [
{
"address": "2MzakdGTEp8SMWEHKwKM4HYv6uNCBXtHpkV",
"amount": "0.000144"
}
],
"senders": [
{
"address": "2N5PcdirZUzKF9bWuGdugNuzcQrCbBudxv1",
"amount": "0.00873472"
}
],
"timestamp": 1582202940,
"transactionHash": "1ec73b0f61359927d02376b35993b756b1097cb9a857bec23da4c98c4977d2b2",
"fee": {
"amount": "0.00016932",
"unit": "BTC"
},
"blockchainSpecific": {
"locktime": 1781965,
"size": 125,
"vSize": 166,
"version": 2,
"vin": [
{
"addresses": [
"2N5PcdirZUzKF9bWuGdugNuzcQrCbBudxv1"
],
"coinbase": "0399991d20706f6f6c2e656e6a6f79626f646965732e636f6d20393963336532346234374747a53e994c4a000001",
"scriptSig": {
"asm": "0014daaf6d5cb86befe42df851a4d1df052e663754c1",
"hex": "160014daaf6d5cb86befe42df851a4d1df052e663754c1",
"type": "scripthash"
},
"sequence": "4294967295",
"txid": "caee978cae255bbe303ac86152679e46113a8b12925aa3afaa312d89d11ccbf8",
"txinwitness": [
"3045022100c11ea5740bcd69f0f68a4914279838014d28923134d18e05c5a5486dfd06cc8c02200dadccec3f07bed0d1040f9e5a155efa5fdd40fc91f92342578d26848da4c6b901"
],
"value": "0.00873472",
"vout": 1
}
],
"vout": [
{
"isSpent": true,
"scriptPubKey": {
"addresses": [
"2N5PcdirZUzKF9bWuGdugNuzcQrCbBudxv1"
],
"asm": "OP_HASH160 ca94af32587de4e5006685ffffc65a818ccd3fbc OP_EQUAL",
"hex": "a914507a5bd8cac1d9efdf4c0a4bfacb3e0abb4f8d1587",
"reqSigs": 1,
"type": "scripthash"
},
"value": "0.000144"
}
]
}
}
]
}
}
In conclusion
In this article, we discussed the object table and JSON output of the Crypto APIs list confirmed crypto transactions by address API. We described the various objects that are returned in the API response and explained their meaning and significance. We also discussed why this information is useful for developers working with the API and how it can be used to access and analyze the details of specific transactions.
Reference
The Crypto APIs list confirmed crypto transactions by address API is a powerful tool that allows developers to access and analyze information about confirmed crypto transactions by address. If you would like to use this API, you can request access to it through the third party data marketplace of Worldindata. This platform provides a simple and convenient way to discover and access a wide range of data sources, including the Crypto APIs list confirmed crypto transactions by address API. To request access, you will need to sign up for a Worldindata account and submit a request through the platform. Once your request is approved, you will be able to use the API to retrieve and analyze data about confirmed crypto transactions.