← previous blocknext block →recent activity
Analyzing
Block #120,070,559
14 transactions · 13 stateful · 2026-11-07 03:17:53 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #120,070,559 · 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
1w02w03w14w25w06w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0acd01b6…91c2
0x264123…670e
6 touches
3 conflicts
0xc2575a0e…ff66
0x8121ee…ee7a
6 touches
3 conflicts
0x816d0352…a531
0xfa2075…314c
6 touches
3 conflicts
0x9a2a3d9d…729e
0x264123…670e
4 touches
1 conflict
0xbb192ad7…8085
0x264123…670e
4 touches
1 conflict
0xc2575a0e…f805
0x8121ee…ee7a
4 touches
1 conflict
0xc2575a0e…f99b
0xf884c7…b285
4 touches
1 conflict
0x816d0352…a531
0x9cd7a2…d1a8
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 0x0acd01b67c…3591c2
Audit this contract →
← previous block·next block →recent activity