← previous blocknext block →recent activity
Analyzing
Block #120,726,159
14 transactions · 13 stateful · 2026-11-09 10:26:41 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #120,726,159 · 14 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
1w03w14w210w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33ef7909…fc8e
0x264123…670e
6 touches
3 conflicts
0x666889a7…968f
0x264123…670e
6 touches
3 conflicts
0x19b59d5a…0ceb
0x264123…670e
4 touches
1 conflict
0x215a6452…18ae
0x264123…670e
4 touches
1 conflict
0x5ee3f950…32bf
0x264123…670e
4 touches
1 conflict
0x813d84af…b474
0x264123…670e
4 touches
1 conflict
0xab07df27…2647
0x264123…670e
4 touches
1 conflict
0xe8b6c85c…44e0
0x264123…670e
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: 0x264123a9…fa670e
3 conflicts on slot 0x33ef79099b…f8fc8e
Audit this contract →
← previous block·next block →recent activity