← previous blocknext block →recent activity
Analyzing
Block #89,711,659
32 transactions · 31 stateful · 2026-07-23 19:13:01 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.34
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,711,659 · 32 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w17w225w326w230w031w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x883e9a5b…0f01
0x34b655…2a6f
6 touches
3 conflicts
0x1e56f6b6…5940
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x315e07b8…9823
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x967297da…ca72
0xd32edf…ff58
5 touches
3 conflicts
0x81561f70…fefd
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
3 conflicts on slot 0x883e9a5bc3…c20f01
Audit this contract →
← previous block·next block →recent activity