← previous blocknext block →recent activity
Analyzing
Block #86,692,128
18 transactions · 14 stateful · 2026-07-09 20:10:13 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,692,128 · 18 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
1w05w06w18w19w215w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x013c31f5…a717
0x34b655…2a6f
6 touches
3 conflicts
0xc7fed9f9…f3a0
0x34b655…2a6f
6 touches
3 conflicts
0xa3a1e8c8…bd5d
0x34b655…2a6f
4 touches
2 conflicts
0x6fc24f20…f3c7
0x34b655…2a6f
4 touches
1 conflict
0xa82f0fe6…4144
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity