← previous blocknext block →recent activity
Analyzing
Block #86,855,511
32 transactions · 24 stateful · 2026-07-10 14:21:53 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,855,511 · 32 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
4w05w16w27w08w111w012w113w214w317w420w521w322w130w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x1941b441…5889
0x34b655…2a6f
8 touches
6 conflicts
0x9355efee…7bcd
0x34b655…2a6f
6 touches
3 conflicts
0xa5ab7b8a…c97b
0x34b655…2a6f
6 touches
3 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
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