← previous blocknext block →recent activity
Analyzing
Block #86,680,546
28 transactions · 27 stateful · 2026-07-09 18:52:58 UTC
Parallelism
82/100
Blocked
33%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,680,546 · 28 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w07w08w19w210w212w316w317w423w024w025w126w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x780d167c…c277
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x4a4c3d20…bd65
0x3bd359…433a
6 touches
3 conflicts
0x0db0aaac…e94d
0x43cf54…7777
6 touches
3 conflicts
0x00000000…0000
0x4a92f8…f3d6
6 touches
3 conflicts
0x80398c66…f3cc
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity