← previous blocknext block →recent activity
Analyzing
Block #86,766,324
20 transactions · 17 stateful · 2026-07-10 04:25:51 UTC
Parallelism
80/100
Blocked
41%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,766,324 · 20 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
1w02w16w07w18w29w211w312w317w018w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae901867…8086
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x4cf39eee…2213
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x4c2e78a1…2f95
0x34b655…2a6f
6 touches
3 conflicts
0xae901867…8085
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
3 conflicts on slot 0xae9018679a…898086
Audit this contract →
← previous block·next block →recent activity