← previous blocknext block →recent activity
Analyzing
Block #89,667,258
49 transactions · 43 stateful · 2026-07-23 15:28:25 UTC
Parallelism
65/100
Blocked
65%
Avg conflicts / tx
2.16
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #89,667,258 · 49 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w07w18w210w011w112w213w315w216w421w522w624w727w928w1029w230w1141w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0x8218911e…3bed
0x34b655…2a6f
12 touches
15 conflicts
0x80656e3b…9240
0x34b655…2a6f
10 touches
10 conflicts
0x95c47f03…f1bb
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 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
36 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity