← previous blocknext block →recent activity
Analyzing
Block #89,589,318
15 transactions · 13 stateful · 2026-07-23 07:04:44 UTC
Parallelism
67/100
Blocked
54%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,589,318 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w08w29w110w111w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd51e027e…7c31
0x34b655…2a6f
6 touches
3 conflicts
0x810a3aa2…0227
0x34b655…2a6f
6 touches
3 conflicts
0xa0efb129…90ce
0x34b655…2a6f
6 touches
3 conflicts
0x4886b3df…67a3
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x80630fb9…a436
0x34b655…2a6f
4 touches
1 conflict
0x885d62cf…32e5
0x34b655…2a6f
4 touches
1 conflict
0x8fb0fecf…cb2f
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 0xd51e027eb7…787c31
Audit this contract →
← previous block·next block →recent activity