← previous blocknext block →recent activity
Analyzing
Block #89,415,030
26 transactions · 20 stateful · 2026-07-22 11:40:30 UTC
Parallelism
88/100
Blocked
30%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,415,030 · 26 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w218w221w123w024w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x003efbe8…2c31
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf36fbf2d…0439
0xd32edf…ff58
5 touches
3 conflicts
0x00f7e3b7…e015
0x188d58…ea8e
4 touches
1 conflict
0x00f7e3b7…e017
0x188d58…ea8e
4 touches
1 conflict
0x1a004c59…980d
0x188d58…ea8e
4 touches
1 conflict
0x1a004c59…980e
0x188d58…ea8e
4 touches
1 conflict
0x36cd3056…b5d4
0x188d58…ea8e
4 touches
1 conflict
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
3 conflicts on slot 0x003efbe8c0…632c31
Audit this contract →
← previous block·next block →recent activity