← previous blocknext block →recent activity
Analyzing
Block #86,946,388
9 transactions · 6 stateful · 2026-07-11 00:29:22 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,946,388 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x94ed0437…073c
0x34b655…2a6f
4 touches
1 conflict
0xdb3774c5…2442
0x34b655…2a6f
4 touches
1 conflict
0x10cab052…8d64
0x34b655…2a6f
2 touches
0 conflicts
0x173337fe…f0af
0x34b655…2a6f
2 touches
0 conflicts
0x2e4e7336…e906
0x34b655…2a6f
2 touches
0 conflicts
0x35d95fb0…db9e
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity