← previous blocknext block →recent activity
Analyzing
Block #86,757,188
20 transactions · 16 stateful · 2026-07-10 03:24:54 UTC
Parallelism
65/100
Blocked
63%
Avg conflicts / tx
1.6
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,757,188 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w49w210w411w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc788862c…c259
0x34b655…2a6f
12 touches
15 conflicts
0x1299b030…e115
0x34b655…2a6f
10 touches
10 conflicts
0x410b84ab…1dbc
0x34b655…2a6f
10 touches
10 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
10 touches
10 conflicts
0x5bb46f6c…7693
0x34b655…2a6f
10 touches
10 conflicts
0x74fce6ad…7895
0x34b655…2a6f
10 touches
10 conflicts
0xefcaccf2…c083
0x34b655…2a6f
10 touches
10 conflicts
0xf806218e…c4da
0x34b655…2a6f
10 touches
10 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
15 conflicts on slot 0xc788862c2e…6ec259
Audit this contract →
← previous block·next block →recent activity