Ledger Details
Transactions
0
Success
0
Total Fees
—
Total XRP
—
XRP Burned
—
Ledger Hash
6824AB22620946E82943372D3FDC6B3CE96E436F51E3FB02ECF01D97D87BA010Parent Hash
2F9CE68948D8B81BDC83DA9A6E9A8B1B58F579842DEB9E27D4092CB13B2B6E73Tx Hashnot retained — the transaction tree root lives in the ledger header, and no header survives for any lost ledger
✓ Cryptographically proven, not merely reported— show the proof
the hash on this page
sits inside a LedgerHashes ledger objectthat object hashes to
AD77EB424FC85BAFDEBF42B139CDD4D16449DAB56096313B24B4E49A6568F8B9+ 24 sibling hashes, 3 levels
3806AF8F22037DE598D30D38C8861FADF391171D26F7DE34ACFA038996EA6BEBwhich is 32,570’s account_hash — its header hashes to
4109C6F2045FC7EFF4CDE8F9905D19C28820D86304080FF886B299F0206E42B5The last value is ledger 32,570’s published hash. Changing any recovered hash would change the root and break it — which is what makes these real rather than reconstructed.
Transactions 0reconstructed from ledger 32,570
No transaction landed here. Every transaction advances its sender’s account, the highest such index anywhere in ledger 32,570 is 32,359, and nothing could overwrite it before the snapshot.
No transaction landed here. Every transaction advances its sender’s account, the highest such index anywhere in ledger 32,570 is 32,359, and nothing could overwrite it before the snapshot. Every field marked — died with the ledger. Reconstructed from the state tree of ledger 32,570 — how this works.