← previous blocknext block →recent activity
Analyzing
Block #86,904,758
13 transactions · 11 stateful · 2026-07-10 19:51:13 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,904,758 · 13 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
4w05w06w17w210w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36890fff…f3d1
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x8dfef5ae…9361
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x37ab49be…3b8b
0x34b655…2a6f
4 touches
1 conflict
0x597cbc5e…88e6
0x34b655…2a6f
4 touches
1 conflict
0x5d0a87fc…c5e4
0x34b655…2a6f
4 touches
1 conflict
0x6b564d99…b9eb
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 0x36890fff7e…d7f3d1
Audit this contract →
← previous block·next block →recent activity