← previous blocknext block →recent activity
Analyzing
Block #89,856,617
24 transactions · 22 stateful · 2026-07-24 07:24:39 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.29
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #89,856,617 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w28w39w410w511w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x92385428…6941
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xf2f67056…fa81
0x34b655…2a6f
8 touches
6 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
8 touches
6 conflicts
0x76196ad0…ce0c
0x34b655…2a6f
8 touches
6 conflicts
0x3d22c439…de6d
0x34b655…2a6f
6 touches
3 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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity