← previous blocknext block →recent activity
Analyzing
Block #86,960,392
13 transactions · 11 stateful · 2026-07-11 02:02:58 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,960,392 · 13 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
1w02w13w27w08w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x23fd130f…5623
0xd32edf…ff58
5 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0363d65e…06d2
0x34b655…2a6f
4 touches
1 conflict
0x6b513f5b…9c3c
0x34b655…2a6f
4 touches
1 conflict
0xa0237ed3…2622
0x34b655…2a6f
4 touches
1 conflict
0xa412324b…90aa
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