Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #208034
Committed on Canton
Participant commits update 122090533d…241e3dImported to the execution layers
Importer applies block #208034 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.
0x02f901f4830e4a258221a6830f4240831e8480830c996994925e8d5ec0b8c417bcadbeae4d7e7f22376003fc80b90184de11ad05000000000000000000000000a2863f93ea4890cb5eb6e7cde5ef25c93b5009a200000000000000000000000041f21e381a70e404854d1f95788208bbc6a8cd7200000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007d1ec6be60000000000000000000000000000000000000000000000000000000007bd1f650000000000000000000000000000000000000000000000000000000000000014000000000000000000000000ac4eaedcb1a003163ed8e83b3959753b0eba845a000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000c001a0bd67412819c3e1d312a2c1e7974f0e47b9bf13251569f84d8c7b7a98f6a98d3fa043dbf0bfe3b258205fcb6ca8ad72cd8302eb66a4dbfb7a7b3c5219f2ac45f270