← previous blocknext block →recent activity
Analyzing
Block #86,683,340
30 transactions · 27 stateful · 2026-07-09 19:11:38 UTC
Parallelism
40/100
Blocked
70%
Avg conflicts / tx
5.17
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #86,683,340 · 30 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w410w511w612w713w814w915w1016w1117w1218w1319w1424w1427w1628w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x727fbce7…0c80
0x34b655…2a6f
32 touches
120 conflicts
0x6e942750…9953
0x34b655…2a6f
32 touches
120 conflicts
0xfaef08b1…0696
0x34b655…2a6f
30 touches
105 conflicts
0x63c900f4…2600
0x34b655…2a6f
28 touches
91 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
28 touches
91 conflicts
0xc368d7fd…aaec
0x34b655…2a6f
28 touches
91 conflicts
0x922c7ebd…6600
0xc8689a…ee79
28 touches
91 conflicts
0xb46ee126…a1a5
0x34b655…2a6f
24 touches
66 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 0x727fbce74b…da0c80
Audit this contract →
← previous block·next block →recent activity