← previous blocknext block →recent activity
Analyzing
Block #89,540,618
22 transactions · 20 stateful · 2026-07-23 01:39:27 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
0.82
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,540,618 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w07w18w29w010w112w113w215w316w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x79180ed2…e9ac
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0x69d0a300…67ef
0x34b655…2a6f
6 touches
3 conflicts
0x4e58f1d6…2fca
0x34b655…2a6f
4 touches
1 conflict
0x55d78f9a…d50b
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity