List XRP (Ripple) Transactions By Block Hash
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.
Path Parameters
-
Requirednetwork 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", "ropsten" are test networks.
-
RequiredblockHash string
Represents the hash of the block, which is its unique identifier. It represents a cryptographic digital fingerprint made by hashing the block header twice through the SHA256 algorithm.
Query parameters
-
Optionalcontext 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. -
Optionallimit integer
Defines how many items should be returned in the response per page basis.
-
Optionaloffset integer
The starting index of the response items, i.e. where the response should start listing the returned items.
Response schema
Content-Type: application/json
The request has been successful.
Object :
-
RequiredapiVersion string
Specifies the version of the API that incorporates this endpoint.
Example : 2021-03-20 -
RequiredrequestId string
Defines the ID of the request. The
requestId
is generated by Crypto APIs and it's unique for every request.Example : 601c1710034ed6d407996b30 -
Optionalcontext 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 -
Requireddata object
-
Requiredlimit integer
Defines how many items should be returned in the response per page basis.
Example : 50 -
Requiredoffset integer
The starting index of the response items, i.e. where the response should start listing the returned items.
Example : 0 -
Requiredtotal integer
Defines the total number of items returned in the response.
Example : 100 -
Requireditems arrayExample : Array ( )
-
OptionaladditionalData string
Represents any additional data that may be needed.
Example : r4CmvbkDWGt9AZmkfuubmiSdsxGZFxAKBY -
OptionaldestinationTag integerExample : 3999472835
-
Requiredindex integer
Represents the index position of the transaction in the specific block.
Example : 3 -
RequiredminedInBlockHeight integer
Represents the hight 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.
Example : 15971358 -
Requiredoffer object
-
Requiredamount string
Defines the amount of the offer.
Example : 8.2365 -
Requiredunit string
Defines the unit of the offer.
Example : XRP
-
-
Requiredrecipients array
Represents an object of addresses that receive the transactions.
-
Requiredaddress string
Represents the hash of the address that receives the funds.
Example : rNUY3X3HovAXuTesTbMh8PAX6CM5V2RzMY -
Requiredamount string
Defines the amount of the received funds as a string.
Example : 0.0001
-
-
Requiredsenders array
Represents an object of addresses that provide the funds.
-
Requiredaddress string
Represents the hash of the address that provides the funds.
Example : rPmPErQe4g9725pcNxJpuvKkdqTESTQ6Tu -
Requiredamount string
Represents the total amount sent by this address including the fee.
Example : 0.0001
-
-
Requiredsequence integer
Defines the transaction input's sequence as an integer, which is is used when transactions are replaced with newer versions before LockTime.
Example : 32568 -
Requiredstatus string
Defines the status of the transaction.
Example : tesSUCCESS -
Requiredtimestamp integer
Defines the exact date/time in Unix Timestamp when this transaction was mined, confirmed or first seen in Mempool, if it is unconfirmed.
Example : 236589 -
RequiredtransactionHash string
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 protocolshash
is different fromtransactionId
for SegWit transactions.Example : ba3bc1337071c8e73b441fe12a1911f4365d7ea82cace7c8ecba3ee9f364978b -
Requiredtype string
Defines the type of the transaction.
Example : Payment -
Requiredfee object
-
Requiredamount string
Defines the amount of the fee.
Example : 2.0325 -
Requiredunit string
Defines the unit of the fee.
Example : XRP
-
-
Requiredreceive object
-
Requiredamount string
Defines the received amount.
Example : 6.2354 -
Requiredunit string
Defines the unit of the received amount.
Example : XRP
-
-
Requiredvalue object
-
Requiredamount string
Defines the amount of the value.
Example : 22.023 -
Requiredunit string
Defines the unit of the value.
Example : XRP
-
-
-