← previous blocknext block →recent activity
Analyzing
Block #89,414,254
28 transactions · 23 stateful · 2026-07-22 11:35:19 UTC
Parallelism
82/100
Blocked
48%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,414,254 · 28 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w211w012w313w115w116w217w318w319w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0xf195ad96…e0c3
0x34b655…2a6f
8 touches
6 conflicts
0x9a2a6ba4…a3b8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xb658103b…163d
0xd32edf…ff58
7 touches
6 conflicts
0x6aa624fd…a852
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity