Skip to main content


NameDescriptionData TypeDomain ValuesPrimary Key?Natural Key?Partition or Cluster Field?Required?Notes
key_hashLedger key hash used to identify expiring contract data or contract code ledger entriesstringYesClusterYes
live_until_ledger_seqLedger sequence the contract or wasm will live untilintegerYes
last_modified_ledgerThe ledger sequence number when the ledger entry (this unique signer for the account) was modified. Deletions do not count as a modification and will report the prior modification sequence numberintegerYesClusterYes
ledger_entry_changeCode that describes the ledger entry change type that was applied to the ledger entry.integerYes
deletedIndicates whether the ledger entry (balance id) has been deleted or not. Once an entry is deleted, it cannot be recovered.booleanYes
batch_idString 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 capabilitiesstringYes
batch_run_dateThe 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.datetimeYes
batch_insert_tsThe 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 backfilltimestampYes
closed_atThe UNIX timestamp of the sequence number's agetimestampYesParitionYes
ledger_sequenceThe unsigned 32-bit ledger number of the sequence number's ageintegerYesYes