← previous blocknext block →recent activity
Analyzing
Block #120,069,645
20 transactions · 18 stateful · 2026-11-07 03:13:17 UTC
Parallelism
85/100
Blocked
28%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #120,069,645 · 20 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
1w02w15w06w07w18w19w218w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x816d0352…a531
0x9cd7a2…d1a8
6 touches
3 conflicts
0x7003a7a5…94b5
0x264123…670e
6 touches
3 conflicts
0xc8526d50…eadc
0x264123…670e
6 touches
3 conflicts
0x69db23d3…ca80
0xae8e0c…e422
6 touches
3 conflicts
0xe7c8cb28…54bd
0x264123…670e
4 touches
2 conflicts
0x386ce9fd…caf1
0x264123…670e
4 touches
2 conflicts
0x00000000…0055
0x1b6862…e19c
4 touches
1 conflict
0x1aa19c07…50ed
0x1b6862…e19c
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: 0x9cd7a28a…02d1a8
3 conflicts on slot 0x816d0352cb…daa531
Audit this contract →
← previous block·next block →recent activity