Skip to main content

Set the replica count

Click + at the top right of a Space’s Tables list to open New Table. Fill in the table type and name, select a replica count under Replicas, and click Save and open.
  • 1 - Standard availability: The default. Lower storage overhead, suitable for data you can rebuild.
  • 3 - Higher availability: Stores multiple copies for better availability during failures, with higher storage overhead.
Replicas selector in New Table with options for 1 and 3 replicas
The replica count is fixed when the table is created and cannot be changed afterward. Derived subtables inherit the main table’s setting.

Set the start height

After saving the schema and before processing any blocks, click the settings icon beside Schema, enter Start Height, and click Save. Once the table has processed blocks, its start height cannot be changed. For example, if the table should cover blocks from 25939925 onward, set its start height to 25939925 before the first write. A small backfill can also keep the default 0.
Start Height dialog opened from the settings icon beside Schema, with the height field and Save button

Check consensus height

Open a block table and find Consensus Height under Overview. The adjacent Completeness by Height chart shows coverage by block height, helping you inspect progress and gaps.
Block table Overview with Consensus Height and Completeness by Height
For programmatic access, use get_consensus_height() in blockdb-py.

Inspect asynchronous write jobs

batch_write() returning True means only that the job was submitted. Each table supporting batch writes has a job table with ID <table_id>._write. Click write under the target table’s Relations to open it.
Asynchronous asset_notes write jobs with succeed status
Read write-job records for a normal table: