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