← previous blocknext block →recent activity
Analyzing
Block #89,585,649
15 transactions · 14 stateful · 2026-07-23 06:40:16 UTC
Parallelism
73/100
Blocked
21%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,585,649 · 15 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
6w07w110w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd51e027e…7c31
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x0712a2c2…d820
0x34b655…2a6f
4 touches
1 conflict
0x6c89dff7…4250
0x065c9d…c394
2 touches
0 conflicts
0x81d53879…0f69
0x065c9d…c394
2 touches
0 conflicts
0xa894db59…d258
0x065c9d…c394
2 touches
0 conflicts
0xf683bd98…d43d
0x065c9d…c394
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity