Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #19133
Committed on Canton
Participant commits update 12204f986b…ada697Imported to the execution layers
Importer applies block #19133 from GatewayHeadStep durations aren't available on this connection, so per-step and total timings are omitted rather than shown as a misleading 0ms. The lifecycle stages above did occur (the Canton↔EVM correlation is confirmed); only the sub-step wall-clock timing is unavailable — it requires a data source that reports distinct step timestamps rather than an atomic commit.
Total
—
Block → Canton commit
—
Step durations aren't available on this connection, so timings are shown as “—” rather than a misleading 0ms. The stages did occur (the Canton↔EVM correlation is confirmed) — only the sub-step wall-clock timing is unavailable, as the sequencer reports the steps as a single atomic commit.
0xf8ac80850f6ca6b0b08259a294d129219e03f0ad695dbb10182802b82adf9ab96c80b84440c10f19000000000000000000000000223c451fbb8c23ae38b3b474d9f4094faec578de00000000000000000000000000000000000000000000003635c9adc5dea00000831c946ea075a6e905f72e4e067cf03f6bf2538d6689605af3ca646d2b249f9919de9800cca01bde2b6bdc696ec46d92ad285a5a49bd921883719c406c50245939b71515b0ca