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