Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #155031
Committed on Canton
Participant commits update 122004a90d…6394dbImported to the execution layers
Importer applies block #155031 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.
0x02f901f4830e4a25820f02830f4240831e8480830799bc94925e8d5ec0b8c417bcadbeae4d7e7f22376003fc80b90184de11ad050000000000000000000000003bd945d969e2a4b76edf8cf09fe6357bb6682f4f00000000000000000000000041f21e381a70e404854d1f95788208bbc6a8cd7200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003eedf6f40000000000000000000000000000000000000000000000001558c5d81a7adf0680000000000000000000000000000000000000000000000000000000000000004000000000000000000000000e0f6d3e2e0dedbf8a37917a2e8aa6343bb395090000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000c080a0f4bb6bbf13d5bb9be29fd4760bf0195b5e5f9c733a96d68f191dd54b586b4364a004d29e65e52b1c55a9d1a234bb19b0412c12f1e2aeeb278cec269fd7e75b8310