Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #144274
Committed on Canton
Participant commits update 122097fd61…cd597cImported to the execution layers
Importer applies block #144274 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.
0x02f901f4830e4a25821af5830f4240831e8480830cba5994925e8d5ec0b8c417bcadbeae4d7e7f22376003fc80b90184de11ad050000000000000000000000003bd945d969e2a4b76edf8cf09fe6357bb6682f4f00000000000000000000000041f21e381a70e404854d1f95788208bbc6a8cd7200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003f4307df000000000000000000000000000000000000000000000000077665cf3148339180000000000000000000000000000000000000000000000000000000000000014000000000000000000000000924e07135a82f034b12537d45845ea554fdbd2e1000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000c001a0d7268b12df5f158dfe6a5e68775458ae744e72a088d5ec9f684ef65f0f24a88aa01905978460ed2ccce17151e8520eaf5e8dce5e07f3e5cbd1482437d7eace639b