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