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