← previous blocknext block →recent activity
Analyzing
Block #86,988,155
13 transactions · 11 stateful · 2026-07-11 05:08:28 UTC
Parallelism
85/100
Blocked
18%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,988,155 · 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
1w04w06w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe2f3517…dfb1
0x34b655…2a6f
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0xbe2f3517…dfb0
0x34b655…2a6f
4 touches
1 conflict
0xfa667abe…bdfc
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xe3f11ed8…a8a6
0x34b655…2a6f
4 touches
1 conflict
0x5f292cab…75fb
0x34b655…2a6f
3 touches
1 conflict
0x0178c2de…b37d
0xb1dbf0…c0d3
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 0xbe2f3517d0…d6dfb1
Audit this contract →
← previous block·next block →recent activity