← previous blocknext block →recent activity
Analyzing
Block #119,296,010
13 transactions · 13 stateful · 2026-11-04 09:53:36 UTC
Parallelism
85/100
Blocked
15%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #119,296,010 · 13 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
1w04w19w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9371684…df38
0x34b655…2a6f
4 touches
1 conflict
0xfcd5e68f…2a12
0x34b655…2a6f
4 touches
1 conflict
0xc8526d50…eadc
0x264123…670e
4 touches
1 conflict
0x8e7fd942…c379
0x34b655…2a6f
4 touches
1 conflict
0x02b40964…6885
0x34b655…2a6f
2 touches
0 conflicts
0x2fde3e82…2035
0x34b655…2a6f
2 touches
0 conflicts
0x3a4f9794…d7b3
0x34b655…2a6f
2 touches
0 conflicts
0x449a8a36…f620
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: Perpl
1 conflict on slot 0xa937168456…4ddf38
Audit this contract →
← previous block·next block →recent activity