Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #5050
Committed on Canton
Participant commits update 122057a89a…33ebe7Imported to the execution layers
Importer applies block #5050 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.
0x02f901eb830e4a2580843b9aca00843b9aca158302d2d78080b9018f6080604052348015600e575f5ffd5b506101738061001c5f395ff3fe608060405234801561000f575f5ffd5b506004361061003f575f3560e01c80633fb5c1cb146100435780638381f58a14610058578063d09de08a14610072575b5f5ffd5b610056610051366004610101565b61007a565b005b6100605f5481565b60405190815260200160405180910390f35b6100566100b4565b5f8190556040518181527f2fd81fd19d3c5c4b396dd13f451dafc8bcac1b3094c49c5fa90e68456323f0e39060200160405180910390a150565b60015f5f8282546100c59190610118565b90915550505f546040519081527f2fd81fd19d3c5c4b396dd13f451dafc8bcac1b3094c49c5fa90e68456323f0e39060200160405180910390a1565b5f60208284031215610111575f5ffd5b5035919050565b8082018082111561013757634e487b7160e01b5f52601160045260245ffd5b9291505056fea2646970667358221220609adf59db766be563862a733556efd21bf48668904a14baf21036ea9c394f2f64736f6c634300081b0033c001a063437a07f6c42d66dc559713c68aa643240ae7e1b570de99f6465e8a12dc6464a00487efd6243dcda10a4831b4a2317bfcba45631657add168f15f00be1020bf96