Module cryptoapis::apis::xrp_ripple_api [−][src]
Enums
struct for typed errors of method get_latest_mined_xrp__ripple_block
struct for typed errors of method get_xrp__ripple_address_details
struct for typed errors of method get_xrp__ripple_block_details_by_block_hash
struct for typed errors of method get_xrp__ripple_block_details_by_block_height
struct for typed errors of method get_xrp__ripple_transaction_details_by_transaction_id
struct for typed errors of method list_xrp__ripple_transactions_by_address
struct for typed errors of method list_xrp__ripple_transactions_by_block_hash
struct for typed errors of method list_xrp__ripple_transactions_by_block_height
Functions
Through this endpoint customers can fetch the last mined XRP block in the blockchain, along with its details. These could include the hash of the specific, the previous and the next block, its transactions count, its height, etc. Since XRP is a different blockchain than Bitcoin and Ethereum, it isn’t unified.
Through this endpoint the customer can receive basic information about a given XRP 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. Since XRP is a different blockchain than Bitcoin and Ethereum, it isn’t unified.
Through this endpoint customers can obtain basic information about a given XRP block (a block on the XRP blockchain), specifically by using the hash parameter. These block details could include the hash of the specific, the previous and the next block, the number of included transactions, etc. Since XRP is a different blockchain than Bitcoin and Ethereum, it isn’t unified.
Through this endpoint customers can obtain basic information about a given XRP block (a block on the XRP blockchain), 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, etc. Since XRP is a different blockchain than Bitcoin and Ethereum, it isn’t unified.
Through this endpoint customers can obtain details about a XRP transaction by the transaction’s unique identifier. Since XRP is a different blockchain than Bitcoin and Ethereum, it isn’t unified.
This endpoint will list XRP transactions by a attribute address. The transactions listed will detail additional information such as hash, height, time of creation in Unix timestamp, etc. Since XRP is a different blockchain than Bitcoin and Ethereum, it isn’t unified. {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 blockHash. The transactions listed will detail additional information such as hash, addresses, time of creation in Unix timestamp, etc. Since XRP is a different blockchain than Bitcoin and Ethereum, it isn’t unified. {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. Since XRP is a different blockchain than Bitcoin and Ethereum, it isn’t unified. {note}Please note that listing data from the same type will apply pagination on the results.{/note}