← previous blocknext block →recent activity
Analyzing
Block #86,988,270
17 transactions · 16 stateful · 2026-07-11 05:09:14 UTC
Parallelism
71/100
Blocked
25%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,988,270 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0xfa667abe…bdfc
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0xe0e480ee…4802
0x34b655…2a6f
6 touches
3 conflicts
0xe0e480ee…4803
0x34b655…2a6f
6 touches
3 conflicts
0x9c55d191…189c
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity