← previous blocknext block →recent activity
Analyzing
Block #86,988,266
18 transactions · 14 stateful · 2026-07-11 05:09:12 UTC
Parallelism
72/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,988,266 · 18 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
6w07w110w111w212w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xfa667abe…bdfc
0x34b655…2a6f
6 touches
3 conflicts
0x453f53a8…e541
0x34b655…2a6f
4 touches
1 conflict
0xb07a0849…3b62
0xb1dbf0…c0d3
4 touches
1 conflict
0x0ee9bb48…53c9
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity