← previous blocknext block →recent activity
Analyzing
Block #86,819,077
11 transactions · 9 stateful · 2026-07-10 10:18:09 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,819,077 · 11 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
1w04w05w16w07w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa37e64f8…ba05
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x0c366266…77e1
0x34b655…2a6f
4 touches
1 conflict
0x2bfb71b5…3a04
0x34b655…2a6f
4 touches
1 conflict
0x2bfb71b5…3a05
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x50e84e6c…287f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0xa37e64f8b9…21ba05
Audit this contract →
← previous block·next block →recent activity