← previous blocknext block →recent activity
Analyzing
Block #120,063,758
18 transactions · 16 stateful · 2026-11-07 02:43:33 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #120,063,758 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w26w07w18w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x947d8e81…ffeb
0x264123…670e
10 touches
10 conflicts
0xc2575a0e…f8ec
0xed3727…f3af
10 touches
10 conflicts
0xc2575a0e…f805
0xed3727…f3af
8 touches
6 conflicts
0x3c4f7092…9681
0xed3727…f3af
6 touches
3 conflicts
0x3c4f7092…9680
0xed3727…f3af
6 touches
3 conflicts
0x816d0352…a531
0x254d30…93bf
6 touches
3 conflicts
0x382d9aa1…8201
0xed3727…f3af
4 touches
1 conflict
0xbe6c835c…1500
0xed3727…f3af
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
10 conflicts on slot 0x947d8e8157…b1ffeb
Audit this contract →
← previous block·next block →recent activity