← previous blocknext block →recent activity
Analyzing
Block #89,518,946
51 transactions · 44 stateful · 2026-07-22 23:14:46 UTC
Parallelism
80/100
Blocked
59%
Avg conflicts / tx
1.51
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #89,518,946 · 51 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
1w02w03w16w27w312w013w114w215w317w418w532w336w440w442w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…0002
0x48cba2…b48b
12 touches
15 conflicts
0x5c16527f…628c
0x34b655…2a6f
8 touches
6 conflicts
0xb566cc65…214d
0xa6afd3…d132
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity