POSTGet Ledgers Within Range
https://web3.nodit.io/v1/xrpl/mainnet/blockchain/getLedgersWithinRangeRetrieves the list of Ledgers within a specific range.
Parameter to specify the target chain for the query.
Parameter to specify the network of the target chain. Supported networks may vary depending on the chain.
Parameter specifying the starting ledger for the query. You can enter one of the following formats:
- ledger index: Enter ledger number as a decimal string
- ledger hash: 64-character hexadecimal string (excluding 0x prefix)
- ledger tag: Enter "earliest" or "latest" (oldest or most recent ledger)
Notes:
- If provided without toLedger, results are queried from this ledger to the latest ledger.
- fromLedger value cannot be greater than toLedger value.
- If fromLedger and toLedger have the same value, only that ledger is queried.
- "latest" for fromLedger is only allowed when toLedger is "latest".
Parameter specifying the ending ledger for the query. You can enter one of the following formats:
- ledger index: Enter ledger number as a decimal string
- ledger hash: 64-character hexadecimal string (excluding 0x prefix)
- ledger tag: Enter "earliest" or "latest" (oldest or most recent ledger)
Notes:
- If provided without fromLedger, results are queried from genesis ledger to this ledger.
- toLedger value cannot be less than fromLedger value.
- If fromLedger and toLedger have the same value, only that ledger is queried.
- "earliest" for toLedger is only allowed when fromLedger is "earliest".
Parameter specifying the start date for the query. Date must follow ISO 8601 format (YYYY-MM-DDThh:mm:ss{time zone}) including seconds.
Notes:
- If provided without toDate, results are queried from this date to the latest block.
- fromDate value must be equal to or earlier than toDate value.
- If fromDate and toDate have the same value, only blocks from that date are queried.
- This field cannot be used together with fromBlock and toBlock.
- If
fromDateandtoDateare not provided, the API queries data from the latest 30 days.
Parameter specifying the end date for the query. Date must follow ISO 8601 format (YYYY-MM-DDThh:mm:ss{time zone}) including seconds.
Notes:
- If provided without fromDate, results are queried from genesis block to this date.
- toDate value must be equal to or later than fromDate value.
- If fromDate and toDate have the same value, only blocks from that date are queried.
- This field cannot be used together with fromBlock and toBlock.
- If
fromDateandtoDateare not provided, the API queries data from the latest 30 days.
The page parameter specifies the data page to query. It accepts values up to 100; for pages exceeding 100, use the cursor pagination method.
The page and cursor parameters cannot be used together. If both page and cursor are empty, cursor pagination is used.
rpp stands for results per page and specifies the page size. You can specify a number greater than 0 and up to 100.
The cursor parameter supports pagination and data navigation between pages. Provide the cursor value from the previous page in the next request to load the next page of data.
The page and cursor parameters cannot be used together. If both page and cursor are empty, cursor pagination is used.
Parameter specifying whether to include the count field in the response. The count field indicates the total number of requested data items. When set to true, the count field is included and response speed may be slower.
Field representing the page number specified in the page parameter. This field is only included in the response when a value greater than 0 is specified for the page parameter.
Field representing the number of results per page specified in the rpp parameter.
A field for cursor pagination. This value must be provided in the next request to load the next page of data.
Field representing the total count of requested data. This field is only included in the response when true is set for the withCount parameter.
Field representing the start of the query range in Date mode. Returned in ISO 8601 format.
Field representing the end of the query range in Date mode. Returned in ISO 8601 format.
Field representing the start block height of the query range in Block mode.
Field representing the end block height of the query range in Block mode.
Field representing the start ledger index of the query range in Ledger mode.
Field representing the end ledger index of the query range in Ledger mode.
Unique identifier of the current ledger, a 256-bit (64-digit hexadecimal) cryptographic hash. Used for ledger data integrity verification and identification.
예: 655EB9D740CC572BFFEC725ABB0AA0D813AAF01C91F8577076F29258794D9445
Integer value indicating the creation order of the ledger, used to identify its position (sequence number) on the network.
예: 95444296
The ledger's close time converted to a Unix timestamp. The close time recorded in the ledger header is expressed in seconds since the Ripple Epoch (January 1, 2000 00:00 UTC), which differs from the Unix Epoch (January 1, 1970 00:00 UTC) by 946,684,800 seconds. Thus ledgerTimestamp is the recorded close time plus 946,684,800 seconds.
예: 1744608171
256-bit (64-digit hexadecimal) hash identifying the ledger immediately preceding the current ledger. References the previous ledger's hash to maintain chain integrity.
예: 45E963AA7A3BB017D626D088C91E6C646B6BBF558DD027AAD974CBBE9A3977D3
256-bit (64-digit hexadecimal) hash summarizing all account state information recorded in the ledger. Used to verify consistency and integrity of account data.
예: 43DA3A81948A7392D14E4DDFB8215372C4B0590E3B28691C599296E4478B12AC
Total quantity of XRP (in XRP units) owned by accounts recorded in the ledger. This value excludes XRP burned as transaction fees. The actual circulating XRP may be lower than this value because some accounts may be in a "black hole" state (accounts with no key).
예: 99986231517.566048
256-bit (64-digit hexadecimal) Merkle tree root hash summarizing all transaction data included in the ledger. Used for transaction history integrity verification.
예: 8BAD7583234AC463E09D6CF160E352DFF5B008FC071DD5226A53809D89E7F409
Integer value indicating the total number of transactions included in the ledger. Used to assess the scale and activity of ledger transaction history.
예: 40
Array of transaction hashes included in the ledger. Each hash is a 256-bit (64-digit hexadecimal) cryptographic hash uniquely identifying a transaction, used for transaction data integrity and identification.
예: 044CD9B107E209F24F5342393F34493E7AFE99AE6F5051F2D75E186F07E1EAE8,0D1DDF6974EA31918EB531F9212FC76BC47BCE9193839496474010D133C0BB1E,1069423CDB7F19E082E6F418C779B19A0126B593832016D134A679EFB752CF0A