← previous blocknext block →recent activity

Analyzing

Block #74,040,194

11 transactions · 10 stateful · 2026-05-12 05:25:07 UTC

Parallelism

82/100

Blocked

20%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,040,194  ·  11 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xf3c1f844…a44f

0x34b655…2a6f

4 touches
1 conflict

0xf6476f21…3580

0x34b655…2a6f

4 touches
1 conflict

0x7b97d40a…09ed

0x34b655…2a6f

4 touches
1 conflict

0xaa3492db…3703

0x34b655…2a6f

4 touches
1 conflict

0xce1ef57a…fd3f

0x34b655…2a6f

4 touches
1 conflict

0x687bc43d…b834

0x065c9d…c394

2 touches
0 conflicts

0x7b9b86c8…b572

0x065c9d…c394

2 touches
0 conflicts

0xbc3c7ea2…29ef

0x065c9d…c394

2 touches
0 conflicts

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: 0x34b6552d…112a6f

1 conflict on slot 0xf3c1f84478…cfa44f

← previous block·next block →recent activity