← previous blocknext block →recent activity
Analyzing
Block #89,709,759
40 transactions · 35 stateful · 2026-07-23 19:03:27 UTC
Parallelism
57/100
Blocked
69%
Avg conflicts / tx
2.33
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #89,709,759 · 40 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
1w03w04w15w06w17w28w112w013w114w015w116w217w319w422w523w624w725w826w227w129w931w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x80656e3b…9240
0x34b655…2a6f
10 touches
10 conflicts
0xe523364b…4a05
0x34b655…2a6f
10 touches
10 conflicts
0x8218911e…3bed
0x34b655…2a6f
8 touches
6 conflicts
0x4cabb80a…46bf
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity