← previous blocknext block →recent activity
Analyzing
Block #119,286,251
21 transactions · 21 stateful · 2026-11-04 09:04:17 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #119,286,251 · 21 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
3w04w05w07w18w211w012w113w114w318w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2575a0e…f9aa
0xf884c7…b285
8 touches
6 conflicts
0x666889a7…968f
0x264123…670e
6 touches
3 conflicts
0x72ba2fdc…939f
0x264123…670e
6 touches
3 conflicts
0x33ef7909…fc8e
0x264123…670e
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x47401a17…8e80
0xf884c7…b285
6 touches
3 conflicts
0x47401a17…8e81
0xf884c7…b285
6 touches
3 conflicts
0xc2575a0e…f805
0xf884c7…b285
6 touches
3 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: 0xf884c763…b5b285
6 conflicts on slot 0xc2575a0e9e…71f9aa
Audit this contract →
← previous block·next block →recent activity