← previous blocknext block →recent activity
Analyzing
Block #86,670,289
20 transactions · 19 stateful · 2026-07-09 17:44:29 UTC
Parallelism
80/100
Blocked
26%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,670,289 · 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
1w03w17w08w011w112w213w317w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x7eab4979…0d6d
0x34b655…2a6f
6 touches
3 conflicts
0xa248a5dd…4a69
0x34b655…2a6f
6 touches
3 conflicts
0x3f60bab6…9752
0x34b655…2a6f
6 touches
3 conflicts
0xab4a9e70…a605
0x34b655…2a6f
6 touches
3 conflicts
0xf761c023…b769
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity