← previous blocknext block →recent activity
Analyzing
Block #120,396,342
18 transactions · 17 stateful · 2026-11-08 06:41:54 UTC
Parallelism
83/100
Blocked
24%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #120,396,342 · 18 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
2w03w14w05w16w015w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x53373f0f…979b
0x264123…670e
4 touches
1 conflict
0x5c76552f…4b64
0x264123…670e
4 touches
1 conflict
0x72ba2fdc…939f
0x264123…670e
4 touches
1 conflict
0xe372ac58…8456
0x264123…670e
4 touches
1 conflict
0xe826d4d6…111c
0x264123…670e
4 touches
1 conflict
0x816d0352…a531
0x49abb9…bfa6
4 touches
1 conflict
0x0f448d0f…de00
0xbb180c…d24f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity