← previous blocknext block →recent activity
Analyzing
Block #86,928,320
22 transactions · 21 stateful · 2026-07-10 22:28:41 UTC
Parallelism
77/100
Blocked
29%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,928,320 · 22 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
3w05w06w09w010w111w112w213w314w417w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x552ac70a…d74b
0x34b655…2a6f
8 touches
6 conflicts
0x95d63682…276c
0x34b655…2a6f
6 touches
3 conflicts
0x95d63682…276d
0x34b655…2a6f
6 touches
3 conflicts
0x8eedf936…a0c3
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xca529dbd…dc62
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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity