← previous blocknext block →recent activity
Analyzing
Block #86,804,207
16 transactions · 11 stateful · 2026-07-10 08:38:47 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,804,207 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w07w08w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55642f63…03d6
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xdec5bfea…d17f
0xa6afd3…d132
4 touches
1 conflict
0x11d629eb…bcd9
0x34b655…2a6f
4 touches
1 conflict
0x27b9caf2…c102
0x34b655…2a6f
4 touches
1 conflict
0x7d7ed9e4…4a59
0x34b655…2a6f
4 touches
1 conflict
0x7d7ed9e4…4a5a
0x34b655…2a6f
4 touches
1 conflict
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 0x55642f6368…8e03d6
Audit this contract →
← previous block·next block →recent activity