Your ideas for the first few fields are correct.
The remainder are as follows:
0 Mgas/s
- million gas processed/s
13399+
- unverified queue size
0
- verified queue size
#2360201
- last imported block number
0/8/25 peers
- number of active peers / number of known peers / configured maximum number of peers (this can be configured up to 50)
9 MiB db
- state database memory used
6 MiB chain
- blockchain cache info memory used
50 MiB queue
- queue memory used (contains information about the queued blocks)
2 MiB sync
- sync memory used (contains information about the connected peers, last imported block, etc.)
I believe the stray Qed
is actually a typo. It should be qed
, which is an argument passed to the tracing to allow for the use of "Panickers". It shouldn't be output by the logs.
The logs are created by the code in informant.rs
.
Edit:
As per the comments, it's far more likely that Qed
stands for "queued".
The snapshot is stored on your disk in a directory like
~/.local/share/io.parity.ethereum/chains/ethereum/db/906a34e69aec8c0d/snapshot/
and is currently around 1.5 GB in size. It contains the latest state at BLOCK
(all accounts, all balances, all contracts, all execution states, etc.) and the last 30_000 blocks before that state.
Best Answer
Some rpc calls in
parity
module would be available:https://wiki.parity.io/JSONRPC-parity-module