← previous blocknext block →recent activity
Analyzing
Block #89,528,024
13 transactions · 12 stateful · 2026-07-23 00:15:24 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.54
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,528,024 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w29w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56b5f5c0…a3ad
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x3b6e959d…158f
0x34b655…2a6f
4 touches
1 conflict
0x402c7c80…f800
0x34b655…2a6f
4 touches
1 conflict
0xf6deafb5…5c25
0x34b655…2a6f
4 touches
1 conflict
0x109d8a52…a7b7
0x34b655…2a6f
4 touches
1 conflict
0xeb0b1d43…9559
0x34b655…2a6f
4 touches
1 conflict
0xf609f09b…f03a
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 0x56b5f5c03e…07a3ad
Audit this contract →
← previous block·next block →recent activity