Module cryptoapis::apis::unified_endpoints_api [−][src]
Enums
struct for typed errors of method get_address_details
struct for typed errors of method get_block_details_by_block_hash
struct for typed errors of method get_block_details_by_block_height
struct for typed errors of method get_fee_recommendations
struct for typed errors of method get_latest_mined_block
struct for typed errors of method get_transaction_details_by_transaction_id
struct for typed errors of method list_transactions_by_address
struct for typed errors of method list_transactions_by_block_hash
struct for typed errors of method list_transactions_by_block_height
Functions
Through this endpoint the customer can receive basic information about a given address based on confirmed/synced blocks only. In the case where there are any incoming or outgoing unconfirmed transactions for the specific address, they will not be counted or calculated here.
Through this endpoint customers can obtain basic information about a given mined block, specifically by using the hash
parameter. These block details could include the hash of the specific, the previous and the next block, its transactions count, its height, etc. Blockchain specific data is information such as version, nonce, size, bits, merkleroot, etc.
Through this endpoint customers can obtain basic information about a given mined block, specifically by using the height
parameter. These block details could include the hash of the specific, the previous and the next block, its transactions count, its height, etc. Blockchain specific data is information such as version, nonce, size, bits, merkleroot, etc.
Through this endpoint customers can obtain fee recommendations. Our fees recommendations are based on Mempool data which makes them much more accurate than fees based on already mined blocks. Calculations are done in real time live. Using this endpoint customers can get gas price for Ethereum, fee per byte for Bitcoin, etc.
Through this endpoint customers can fetch the last mined block in a specific blockchain network, along with its details. These could include the hash of the specific, the previous and the next block, its transactions count, its height, etc. Blockchain specific data is information such as version, nonce, size, bits, merkleroot, etc.
Through this endpoint customers can obtain details about a transaction by the transaction’s unique identifier. In UTXO-based protocols like BTC there are attributes such as transactionId
and transaction hash
. They still could be different. In protocols like Ethereum there is only one unique value and it’s hash
.
This endpoint will list transactions by an attribute address
. The transactions listed will detail additional information such as hash, height, time of creation in Unix timestamp, etc. {note}Please note that listing data from the same type will apply pagination on the results.{/note}
This endpoint will list transactions by an attribute transactionHash
. The transactions listed will detail additional information such as addresses, height, time of creation in Unix timestamp, etc. {note}Please note that listing data from the same type will apply pagination on the results.{/note}
This endpoint will list transactions by an attribute blockHeight
. The transactions listed will detail additional information such as hash, addresses, time of creation in Unix timestamp, etc. {note}Please note that listing data from the same type will apply pagination on the results.{/note}