← previous blocknext block →recent activity
Analyzing
Block #89,676,647
35 transactions · 32 stateful · 2026-07-23 16:16:26 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
1.86
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #89,676,647 · 35 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w110w011w112w215w216w320w421w522w623w725w826w927w933w834w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
18 touches
36 conflicts
0x81561f70…fefd
0x34b655…2a6f
16 touches
28 conflicts
0x7aad02c6…b979
0x34b655…2a6f
14 touches
21 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x183a32c3…5ef2
0x34b655…2a6f
10 touches
10 conflicts
0x8218911e…3bed
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
36 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity