← previous blocknext block →recent activity
Analyzing
Block #86,847,776
45 transactions · 35 stateful · 2026-07-10 13:30:08 UTC
Parallelism
64/100
Blocked
71%
Avg conflicts / tx
2.51
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #86,847,776 · 45 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w210w011w112w214w315w016w117w218w319w420w521w622w723w825w926w1027w1128w1234w335w236w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
26 touches
78 conflicts
0x45ea7a97…bbb3
0x34b655…2a6f
10 touches
10 conflicts
0x8eef368f…aa21
0x34b655…2a6f
10 touches
10 conflicts
0x2b268fa9…eba2
0x34b655…2a6f
8 touches
6 conflicts
0x38c6ff01…689f
0x34b655…2a6f
8 touches
6 conflicts
0x414ca622…37ab
0x34b655…2a6f
8 touches
6 conflicts
0x4e3abeff…18eb
0x34b655…2a6f
8 touches
6 conflicts
0x574628e9…dcc3
0x34b655…2a6f
8 touches
6 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