← previous blocknext block →recent activity
Analyzing
Block #86,921,565
22 transactions · 18 stateful · 2026-07-10 21:43:32 UTC
Parallelism
73/100
Blocked
50%
Avg conflicts / tx
0.55
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,921,565 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w17w08w110w111w213w114w315w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bd6b33e…9557
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x35d95fb0…db9e
0x34b655…2a6f
4 touches
1 conflict
0x35d95fb0…db9f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x58627b98…92ad
0x34b655…2a6f
4 touches
1 conflict
0x59c89f2b…2f10
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
6 conflicts on slot 0x6bd6b33ee8…919557
Audit this contract →
← previous block·next block →recent activity