← previous blocknext block →recent activity
Analyzing
Block #89,597,399
9 transactions · 8 stateful · 2026-07-23 07:58:44 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,597,399 · 9 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
3w04w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc516fef7…841c
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x09de9193…cc8c
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x22af2208…099e
0x34b655…2a6f
2 touches
0 conflicts
0x418f95cd…1512
0x34b655…2a6f
2 touches
0 conflicts
0x63a8652c…5b43
0x34b655…2a6f
2 touches
0 conflicts
0x63a8652c…5b44
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 0xc516fef749…a5841c
Audit this contract →
← previous block·next block →recent activity