← previous blocknext block →recent activity
Analyzing
Block #86,660,309
31 transactions · 22 stateful · 2026-07-09 16:37:55 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.35
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,660,309 · 31 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w07w18w211w012w019w320w422w530w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x250c8181…eef2
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x4e862605…edc4
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x727fbce7…0c80
0x34b655…2a6f
4 touches
1 conflict
0x72f58db9…dc77
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 0x250c8181cb…57eef2
Audit this contract →
← previous block·next block →recent activity