← previous blocknext block →recent activity
Analyzing
Block #86,768,126
30 transactions · 26 stateful · 2026-07-10 04:37:54 UTC
Parallelism
67/100
Blocked
58%
Avg conflicts / tx
1.33
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,768,126 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w210w011w112w215w316w417w519w120w221w623w724w827w728w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x216ffe66…1f94
0x34b655…2a6f
10 touches
10 conflicts
0xac3e4969…39e9
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x0d9c5df5…66d4
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x5e67eb31…015b
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0x216ffe6648…bf1f94
Audit this contract →
← previous block·next block →recent activity