Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #110910
Committed on Canton
Participant commits update 1220b8c79d…227e25Imported to the execution layers
Importer applies block #110910 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.
0x02f901f4830e4a25820459830f4240831e84808307338394925e8d5ec0b8c417bcadbeae4d7e7f22376003fc80b90184de11ad05000000000000000000000000a2863f93ea4890cb5eb6e7cde5ef25c93b5009a200000000000000000000000041f21e381a70e404854d1f95788208bbc6a8cd7200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000008290f71230000000000000000000000000000000000000000000000008b71d02a709f23560000000000000000000000000000000000000000000000000000000000000004000000000000000000000000e0f6d3e2e0dedbf8a37917a2e8aa6343bb395090000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000c080a096280b922ec85e7bccdd0678557ba0d311c348eaf05b9c8f927f283d00e31e7fa05f1c990576003507eb7986e26c890e475bdd2a9c76eed12993a1a3c63f33bd09