← previous blocknext block →recent activity
Analyzing
Block #86,688,286
25 transactions · 23 stateful · 2026-07-09 19:44:38 UTC
Parallelism
72/100
Blocked
52%
Avg conflicts / tx
1.6
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,688,286 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w410w511w615w417w623w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x957c875f…b3f9
0x34b655…2a6f
8 touches
6 conflicts
0xb2fa1675…4e07
0x34b655…2a6f
8 touches
6 conflicts
0x26c3abf6…249d
0x34b655…2a6f
6 touches
3 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
6 touches
3 conflicts
0x3d51c4f1…652d
0x34b655…2a6f
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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity