← previous blocknext block →recent activity
Analyzing
Block #86,983,108
21 transactions · 19 stateful · 2026-07-11 04:34:44 UTC
Parallelism
81/100
Blocked
42%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,983,108 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w210w011w112w113w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x155dff63…2af8
0x34b655…2a6f
8 touches
6 conflicts
0x90d83c92…630e
0xd32edf…ff58
7 touches
6 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0x2bfb71b5…3a05
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9a287655…f785
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
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
6 conflicts on slot 0x155dff638e…a62af8
Audit this contract →
← previous block·next block →recent activity