← previous blocknext block →recent activity
Analyzing
Block #86,695,405
23 transactions · 17 stateful · 2026-07-09 20:32:05 UTC
Parallelism
78/100
Blocked
53%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,695,405 · 23 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
1w02w15w07w18w210w211w112w313w420w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7279da7…774b
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x427d1120…4eb1
0x34b655…2a6f
6 touches
3 conflicts
0x1535d171…c68b
0x34b655…2a6f
4 touches
1 conflict
0x67a56c8b…f955
0x34b655…2a6f
4 touches
1 conflict
0x7da4bbdc…0d30
0x34b655…2a6f
4 touches
1 conflict
0x92b49f44…ee4f
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 0xa7279da72b…51774b
Audit this contract →
← previous block·next block →recent activity