← previous blocknext block →recent activity
Analyzing
Block #120,076,834
13 transactions · 11 stateful · 2026-11-07 03:49:30 UTC
Parallelism
77/100
Blocked
18%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #120,076,834 · 13 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
2w04w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8526d50…eadc
0x264123…670e
4 touches
1 conflict
0x69db23d3…ca80
0xae8e0c…e422
4 touches
1 conflict
0xa0c451b7…a800
0xae8e0c…e422
4 touches
1 conflict
0xa0c451b7…a801
0xae8e0c…e422
4 touches
1 conflict
0xa0c451b7…a802
0xae8e0c…e422
4 touches
1 conflict
0xc2575a0e…f805
0xae8e0c…e422
4 touches
1 conflict
0xc2575a0e…0f80
0xae8e0c…e422
4 touches
1 conflict
0xc2575a0e…0fd0
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
1 conflict on slot 0xc8526d50f8…a1eadc
Audit this contract →
← previous block·next block →recent activity