← previous blocknext block →recent activity
Analyzing
Block #89,598,058
13 transactions · 12 stateful · 2026-07-23 08:03:08 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,598,058 · 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
2w03w04w17w29w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xf1cc9519…84c1
0x34b655…2a6f
4 touches
1 conflict
0x2e5d2545…fbfa
0x34b655…2a6f
4 touches
1 conflict
0x807bf45f…5016
0x34b655…2a6f
4 touches
1 conflict
0x826cce18…251c
0x34b655…2a6f
4 touches
1 conflict
0x9de538e5…7632
0x34b655…2a6f
4 touches
1 conflict
0x9de538e5…7633
0x34b655…2a6f
4 touches
1 conflict
0xb550abea…2729
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity