Reconnecting to XRPL feedWaiting for dataFollower deployment
XRPL operations
Operational visibility for xLedgRS deployments.
Track ledger freshness, sync posture, persisted leaf growth, fee conditions, and replay health from a single operator-facing surface designed for infrastructure teams, exchanges, and enterprise XRPL environments.
Validated ledger
—
waiting for ledger hash
History upper
—
history range unavailable
Ledger gap
—
validated seq minus history upper
Persisted state leaves
—
waiting for leaf ingest rate
Live source
Node identity
offline
RPC targetunresolved
Last payloadwaiting
Public node key—
Validator keynot loaded
Runtime versionxLedgRS V1 Beta
Network—
Uptime—
Memory—
Operational overview
This dashboard presents live node signals for network connectivity, state coverage, persistence, replay, and fee conditions so teams can assess service posture quickly during deployment, validation, and day-to-day operations.
Ledger freshness
—
healthy under 30s
Peer mesh
0 peers
targeting 20+ connections
History coverage
—
history upper vs validated ledger
Queue load
—
0 / 0 tx slots
XRPL cadence
Recent ledger closes
Stream delta
waiting
Latest public close
—
Waiting for ledger stream
Validated close
—
The node’s current validated ledger close time from `server_info`.
Open-ledger fee
—
— versus — base fee.
State storage
State persistence
Persisted state leaves
—
Directly reported by the running xLedgRS node as persisted account-state leaves.
Leaf persist ratemeasuring
History range—
History gap to tip—
Storage engine—
SQLite ledgers—
SQLite transactions—
Runtime
Node posture
Server stateWaiting for data
Load factor—
Validation quorum—
Base reserve10 XRP
Owner reserve2 XRP
Base fee0 XRP
Fee lane
Queue and pricing
Current ledger size
0
Transactions currently lining up for the open-ledger window.
Expected ledger size
0
Target capacity before fee escalation begins to increase materially.
Base fee—
Median fee—
Open-ledger fee—
Current queue size0
Max queue size0
Replay integrity
Follower diagnostics
Replay activation
Replay metrics appear once the node completes its current sync phase and transitions into follower replay. Until then, this panel remains in standby rather than presenting incomplete operational totals.