← previous blocknext block →recent activity
Analyzing
Block #89,598,075
23 transactions · 22 stateful · 2026-07-23 08:03:15 UTC
Parallelism
74/100
Blocked
55%
Avg conflicts / tx
1.22
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,598,075 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w07w18w19w410w211w316w418w219w521w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x3dbe80c7…2595
0xd32edf…ff58
9 touches
10 conflicts
0x4e37574f…4145
0x34b655…2a6f
8 touches
6 conflicts
0xecbb3355…9640
0x34b655…2a6f
6 touches
3 conflicts
0x17a7f697…dcb3
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity