Ledger Details
Transactions
0
Success
0
Total Fees
—
Total XRP
—
XRP Burned
—
Ledger Hash
8BBBD0230172632B3D7AF8E8282332D40C3B9C2222AD03880762E1ACF650EFABParent Hash
971493E9501311022947245C5968237D89BB2EB0F967980616C0650122006C6DTx 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.