← previous blocknext block →recent activity
Analyzing
Block #86,673,749
94 transactions · 55 stateful · 2026-07-09 18:07:36 UTC
Parallelism
79/100
Blocked
71%
Avg conflicts / tx
2.27
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #86,673,749 · 94 txs across 20 waves · depth 20
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w47w59w610w711w822w831w932w936w240w1042w1059w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
26 touches
78 conflicts
0x27ecb00e…993b
0xd32edf…ff58
23 touches
66 conflicts
0x62030a81…91be
0x34b655…2a6f
14 touches
21 conflicts
0x7e77d98d…2921
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x503b3a72…f6df
0x34b655…2a6f
12 touches
15 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 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
78 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity