← previous blocknext block →recent activity
Analyzing
Block #74,476,934
11 transactions · 9 stateful · 2026-05-14 05:50:42 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,476,934 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf3981be5…2c47
0x34b655…2a6f
6 touches
3 conflicts
0xab621973…cc16
0x34b655…2a6f
4 touches
1 conflict
0xfac43f12…b842
0x34b655…2a6f
4 touches
1 conflict
0x849f3e33…c095
0x34b655…2a6f
4 touches
1 conflict
0x0d2947c3…98d6
0x34b655…2a6f
2 touches
0 conflicts
0x40b3d30e…7b92
0x34b655…2a6f
2 touches
0 conflicts
0x8d13ecc1…980f
0x34b655…2a6f
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: Perpl
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity