← previous blocknext block →recent activity
Analyzing
Block #120,413,145
20 transactions · 15 stateful · 2026-11-08 08:06:42 UTC
Parallelism
90/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #120,413,145 · 20 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w014w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8526d50…eadc
0x264123…670e
4 touches
1 conflict
0xc2575a0e…0f80
0xae8e0c…e422
4 touches
1 conflict
0x0c17637b…0280
0xf3fb2e…41eb
4 touches
1 conflict
0x0c17637b…0281
0xf3fb2e…41eb
4 touches
1 conflict
0x0c17637b…0283
0xf3fb2e…41eb
4 touches
1 conflict
0x4beeaa17…a32f
0x34b655…2a6f
2 touches
0 conflicts
0x4de38143…795c
0x34b655…2a6f
2 touches
0 conflicts
0x4feae968…6030
0x34b655…2a6f
2 touches
0 conflicts
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