How the XRP Ledger closes a ledger

No miners, no proof of work. A set of validators you choose to trust agrees on which transactions go in, roughly every four seconds.

Read how it works

Click a step on the right, or use the arrow keys, to jump to it. Move your mouse to shift the view.

Just validated

    pending transaction proposal validated deferred to next ledger provisional, in the open ledger in a validated ledger included but failed, fee burned on the default UNL (inner ring)
    Currencies used, by share of each ledger Waiting for the first full ledger
    How this is counted

    Counts successful payments and DEX orders. Each one counts once for every currency it moves, so an order swapping RLUSD for XRP counts toward both. Tokens have no common price here, so this shows how often each currency is used, not how much value moved.

      Currencies used in each ledger since you connected
      LedgerTransactions per currency
      Transactions per ledger Waiting for the first ledger
      • succeeded
      • bounced (failed, fee burned)
      • before you connected

      Use the left and right arrow keys to read each ledger's count.

      Transactions in each recent ledger
      LedgerTransactionsSucceededBouncedClosed
      Ledger chain 0 tx in open ledger 0.000000 XRP burned 0 of 0 validators agree

        The parts that make this work

        Validators and the UNL

        Anyone can run a validator, but running one doesn't give you influence. Influence comes from other people putting your validator on their Unique Node List. Most servers use a published default list of around 35 validators, run by universities, exchanges, and independent operators. Ripple runs one of them.

        Why the threshold climbs

        Starting at 50 % and ending at 80 % lets validators quickly discard transactions few peers have seen, without stalling on a single disagreement. Different servers can have slightly different UNLs and still converge, as long as the lists overlap enough. A transaction that misses one ledger is retried in the next.

        Finality in seconds

        Because a ledger only counts once 80 % of trusted validators have signed its hash, there's no waiting for confirmations to pile up. A payment that appears in a validated ledger is settled. Ledgers close every 3 to 5 seconds, and each one records the hash of the one before it.

        What a transaction costs

        The base fee is 10 drops, which is 0.00001 XRP. It's a spam deterrent, not a reward, and it's burned. When the network is busy the fee rises for everyone, which is what makes flooding the ledger expensive. Accounts also lock a small reserve of XRP to exist on the ledger.

        What live mode shows

        Live mode connects to a public XRP Ledger server over WebSocket and draws mainnet events as they arrive. Each violet dot is a real transaction the server has provisionally applied to its open ledger. The inner ring holds the validators on the default UNL published at vl.ripple.com; the outer ring fills with every other validator the server hears from. A beam means that validator has just signed the next ledger. The ledger numbers, hashes, transaction counts and burned fees are real. The server doesn't say which validator first received a transaction, so transactions fly straight into the open ledger.

        What the animation simplifies

        Real consensus runs continuously: validators keep exchanging proposals while the ledger is open, and "rounds" are timing windows rather than discrete steps. The counts and transaction volumes here are illustrative. Read the XRPL consensus documentation for the full protocol.