Interpreting Console Out

The following raw data is logged to the v3 console for blocks that are accepted to the strong chain. For early blocks the console skips lines in order to not slow down the synchronization. However all entries are written to the debug log. For specific examples see Small Server Performance and Big Server Performance.

Fields

block

The height of the block in the strong chain.

txs

The number of transactions in the block, including the coinbase.

ins

The number of inputs in the block, including the coinbase.

wms

The time (in milliseconds) the block waited to begin validation, after having been downloaded and deserialized. Delays are primarily the result of preceding block or transaction validation, as full validation is ordered. This is typically zero unless blocks are very closely spaced.

vms

The total time (in milliseconds) to validate the block. This includes all time from the beginning of deserialization through completion of script checks with the exception of wait time (wms).

vµs

The total time (in microseconds) to validate the block, divided by the number of inputs, or vms * 1000 ÷ ins.

rµs

The total time (in microseconds) to deserialize the block, divided by the number of inputs.

cµs

The total time (in microseconds) to perform context-free checks (block check), divided by the number of inputs.

pµs

The total time (in microseconds) to populate data necessary for contextual checks, divided by the number of inputs.

aµs

The total time (in microseconds) to perform contextual checks excluding script execution (block accept), divided by the number of inputs.

sµs

The total time (in microseconds) to perform script validation (block connect), divided by the number of inputs.

dµs

The total time (in microseconds) to deposit the block and indexing into the store following successful validation, divided by the number of inputs. If write flushing is enabled that time is included.

efficiency

The fraction of non-coinbase transactions that were found in the transaction pool. This value will increase toward 100% as the node collects unconfirmed transactions from the network. Script validation cost is nearly eliminated when efficiency is close to 100%. Transactions are never discarded, so this may be non-zero upon restart. Increasing node.minimum_byte_fee_satoshis decreases efficiency. Efficiency may be low if transactions are being missed because there are too few peers. Reduced efficiency will also occur when transactions are mined before having been broadcast to the network.