Skip to main content
Schema: stellar.core Table: fact_ledgers Type: Base Table Each ledger stores the state of the network at a given point in time and contains all changes applied to the network - transactions, operations, etc. This table summarizes the actions taken within a single ledger and is relevant in determining high level network conditions. Learn more about Stellar ledgers: https://developers.stellar.org/docs/learn/fundamentals/stellar-data-structures/ledgers

Columns

Column NameData TypeDescription
SEQUENCENUMBERThe sequence number that corresponds to the individual ledgers. As ledgers are written to the network, the sequence is incremented by 1
LEDGER_HASHTEXTThe hex-encoded SHA-256 hash that represents the ledger’s XDR-encoded form.
PREVIOUS_LEDGER_HASHTEXTThe hex-encoded SHA-256 hash of the ledger that immediately precedes this ledger.
TRANSACTION_COUNTNUMBERThe number of successful transactions submitted and completed by the network in this ledger.
OPERATION_COUNTNUMBERThe total number of successful operations applied to this ledger.
CLOSED_ATTIMESTAMP_NTZTimestamp when the ledger was closed and committed to the network. Ledgers are expected to close ~every 5 seconds.
BLOCK_TIMESTAMPTIMESTAMP_NTZA clone of closed_at for join convenience.
IDNUMBERUnique identifier for the ledger
TOTAL_COINSNUMBERTotal number of lumens in circulation
FEE_POOLNUMBERThe sum of all transaction fees
BASE_FEENUMBERThe fee (in stroops) the network charges per operation in a transaction for the given ledger. The minimum base fee is 100, with the ability to increase if transaction demand exceeds ledger capacity. When this occurs, the ledger enters surge pricing.
BASE_RESERVENUMBERThe reserve (in stroops) the network requires an account to retain as a minimum balance in order to be a valid account on the network. The current minimum reserve is 10 XLM.
MAX_TX_SET_SIZENUMBERThe maximum number of operations that Stellar validator nodes have agreed to process in a given ledger. Since Protocol 11, ledger capacity has been measured in operations rather than transactions.
PROTOCOL_VERSIONNUMBERThe protocol verstion that the Stellar network was running when this ledger was committed. Protocol versions are released ~every 6 months.
SUCCESSFUL_TRANSACTION_COUNTNUMBERThe number of successful transactions submitted and completed by the network in this ledger
FAILED_TRANSACTION_COUNTNUMBERThe number of failed transactions submitted to the network in this ledger. The transaction was still paid for but contained an error that prevented it from executing
TX_SET_OPERATION_COUNTNUMBERThe total number of operations in the transaction set for this ledger, including failed transactions.
BATCH_IDTEXTString representation of the run id for a given DAG in Airflow. Takes the form of “scheduled__<batch_end_date>-<dag_alias>”. Batch ids are unique to the batch and help with monitoring and rerun capabilities.
BATCH_RUN_DATETIMESTAMP_NTZThe start date for the batch interval. When taken with the date in the batch_id, the date represents the interval of ledgers processed. The batch run date can be seen as a proxy of closed_at for a ledger.
BATCH_INSERT_TSTIMESTAMP_NTZThe timestamp in UTC when a batch of records was inserted into the database. This field can help identify if a batch executed in real time or as part of a backfill. The timestamp should not be used during ad hoc analysis and is useful for data engineering purposes.
SOROBAN_FEE_WRITE_1KBNUMBERThe fee associated with writing 1KB of data to the Soroban ledger.The write fee is dynamic fee that grows linearly with the size of the ledger. The write fee for a given ledger is recorded in the ledger header and has a direct relationship to the bucketlist size of the ledger db.
NODE_IDTEXTThe id of winning validator node which is allowed to write transaction set to the network. The winning validator is decided by the network.
SIGNATURETEXTThe signing hash of the validator node which writes the transaction set to the network.This signature ensures the integrity and authenticity of the ledger, confirming that it has not been tampered with.
TOTAL_BYTE_SIZE_OF_BUCKET_LISTNUMBERTotal size in bytes of the bucket list
FACT_LEDGERS_IDTEXTUnique primary key for the dimension table, used as the main identifier for each record.
INSERTED_TIMESTAMPTIMESTAMP_NTZTimestamp when this record was inserted.
MODIFIED_TIMESTAMPTIMESTAMP_NTZTimestamp when this record was last modified.