← previous blocknext block →recent activity
Analyzing
Block #86,632,386
57 transactions · 45 stateful · 2026-07-09 13:30:05 UTC
Parallelism
60/100
Blocked
80%
Avg conflicts / tx
3.65
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #86,632,386 · 57 txs across 23 waves · depth 23
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w18w19w211w312w413w420w021w137w438w240w544w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
32 touches
120 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0x1941b441…5889
0x34b655…2a6f
14 touches
21 conflicts
0xa29182a1…c12c
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x8eb0ac6b…a73a
0x34b655…2a6f
10 touches
10 conflicts
0x69d502ef…f98f
0xd32edf…ff58
9 touches
10 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
120 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity