← previous blocknext block →recent activity
Analyzing
Block #86,625,222
21 transactions · 18 stateful · 2026-07-09 12:42:09 UTC
Parallelism
71/100
Blocked
39%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,625,222 · 21 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
1w03w16w07w18w210w311w012w415w016w119w020w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8388eab6…83ff
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x22bc4ea4…5c8a
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x1951ee47…540f
0x34b655…2a6f
6 touches
3 conflicts
0x9ad66bbf…929c
0x34b655…2a6f
6 touches
3 conflicts
0xba559de1…6d2c
0x34b655…2a6f
6 touches
3 conflicts
0xc0b9bd73…7f1c
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
6 conflicts on slot 0x8388eab63f…1e83ff
Audit this contract →
← previous block·next block →recent activity