← previous blocknext block →recent activity
Analyzing
Block #89,528,222
12 transactions · 11 stateful · 2026-07-23 00:16:43 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,528,222 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56b5f5c0…a3ad
0x34b655…2a6f
4 touches
1 conflict
0x5cedf778…a79c
0x34b655…2a6f
4 touches
1 conflict
0x20f31112…0f02
0x34b655…2a6f
2 touches
0 conflicts
0x220a8541…6431
0x34b655…2a6f
2 touches
0 conflicts
0x32dc06bf…cb27
0x34b655…2a6f
2 touches
0 conflicts
0x4106304d…ae96
0x34b655…2a6f
2 touches
0 conflicts
0x52b3805e…704e
0x34b655…2a6f
2 touches
0 conflicts
0x53355553…2976
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x56b5f5c03e…07a3ad
Audit this contract →
← previous block·next block →recent activity