← previous blocknext block →recent activity
Analyzing
Block #86,686,211
24 transactions · 20 stateful · 2026-07-09 19:30:48 UTC
Parallelism
83/100
Blocked
30%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,686,211 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w08w19w210w316w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7e45018…b59c
0x34b655…2a6f
8 touches
6 conflicts
0xa42e8482…b88f
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x288bc578…318e
0x34b655…2a6f
6 touches
3 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
6 touches
3 conflicts
0x4327afd2…1b3a
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
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 0xa7e45018ba…2fb59c
Audit this contract →
← previous block·next block →recent activity