Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #117855
Committed on Canton
Participant commits update 12200b7afa…f76645Imported to the execution layers
Importer applies block #117855 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.
0x02f901f4830e4a25820f8c830f4240831e8480830c98fd94925e8d5ec0b8c417bcadbeae4d7e7f22376003fc80b90184de11ad05000000000000000000000000a87685dc3f504463f049f6d8deed800ca6f8806800000000000000000000000041f21e381a70e404854d1f95788208bbc6a8cd7200000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001c5b2d43800000000000000000000000000000000000000000000000000000000054df0300000000000000000000000000000000000000000000000000000000000000014000000000000000000000000214a0c5ed66aa4b8ae836500b688518fcc03f50f000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000c001a09e768130601609757855e57d5e04d93c1f3d89f2ca71aaa262c05f10fc2adf32a01377c711e5fdc9d65b98e3e9813d32073cb1178ea9e2d1d144645befdf3edcb4