← previous blocknext block →recent activity
Analyzing
Block #89,710,526
13 transactions · 11 stateful · 2026-07-23 19:07:18 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,710,526 · 13 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
2w06w17w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x70e3da66…674a
0x34b655…2a6f
4 touches
1 conflict
0x4ab0fef9…caef
0x34b655…2a6f
2 touches
0 conflicts
0x51028c5e…235c
0x34b655…2a6f
2 touches
0 conflicts
0x688cb60f…0e7a
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
3 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity