← previous blocknext block →recent activity
Analyzing
Block #86,792,261
15 transactions · 9 stateful · 2026-07-10 07:18:58 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,792,261 · 15 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
1w02w16w07w18w29w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xe8927855…7e59
0x34b655…2a6f
4 touches
1 conflict
0x945befa9…67b4
0x34b655…2a6f
4 touches
1 conflict
0x82f08cb8…4d95
0x34b655…2a6f
4 touches
1 conflict
0x82f08cb8…4d94
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x728cb046…11ae
0x34b655…2a6f
4 touches
1 conflict
0x7017d770…abbd
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
3 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity