← previous blocknext block →recent activity
Analyzing
Block #74,518,955
16 transactions · 14 stateful · 2026-05-14 10:31:50 UTC
Parallelism
81/100
Blocked
43%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,518,955 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w17w08w19w010w214w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c389468…6b0e
0x34b655…2a6f
6 touches
3 conflicts
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0xc3d17d0c…3649
0x065c9d…c394
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x1eb0fab5…3517
0x34b655…2a6f
4 touches
1 conflict
0x74871f7d…4da8
0x34b655…2a6f
4 touches
1 conflict
0x77100a2a…91a4
0x34b655…2a6f
4 touches
1 conflict
0x8d0e98f3…7ba0
0x34b655…2a6f
4 touches
1 conflict
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: Perpl
3 conflicts on slot 0x1c38946843…a16b0e
Audit this contract →
← previous block·next block →recent activity