← previous blocknext block →recent activity
Analyzing
Block #89,551,171
18 transactions · 18 stateful · 2026-07-23 02:50:02 UTC
Parallelism
56/100
Blocked
44%
Avg conflicts / tx
1.06
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #89,551,171 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w28w39w010w411w512w115w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69d0a300…67ef
0x34b655…2a6f
8 touches
6 conflicts
0xd51e027e…7c31
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0x793d86d7…acc4
0x34b655…2a6f
4 touches
1 conflict
0x7fb26cf8…5172
0x34b655…2a6f
4 touches
1 conflict
0x899723a2…657b
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
6 conflicts on slot 0x69d0a3001a…3467ef
Audit this contract →
← previous block·next block →recent activity