← previous blocknext block →recent activity
Analyzing
Block #120,070,585
18 transactions · 17 stateful · 2026-11-07 03:18:01 UTC
Parallelism
72/100
Blocked
24%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #120,070,585 · 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
2w03w05w07w19w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33ef7909…fc8e
0x264123…670e
8 touches
6 conflicts
0x666889a7…968f
0x264123…670e
6 touches
3 conflicts
0xc2575a0e…0f80
0xae8e0c…e422
4 touches
1 conflict
0x7ff69c25…f18f
0x264123…670e
4 touches
1 conflict
0xbb192ad7…8085
0x264123…670e
4 touches
1 conflict
0xc2575a0e…ff66
0x8121ee…ee7a
4 touches
1 conflict
0x17b469e6…7d00
0xae8e0c…e422
4 touches
1 conflict
0x17b469e6…7d01
0xae8e0c…e422
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
6 conflicts on slot 0x33ef79099b…f8fc8e
Audit this contract →
← previous block·next block →recent activity