← previous blocknext block →recent activity
Analyzing
Block #89,707,318
10 transactions · 9 stateful · 2026-07-23 18:51:07 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,707,318 · 10 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
1w03w15w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x12978194…d32f
0x34b655…2a6f
6 touches
3 conflicts
0x19cbeea8…ecf3
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
2 touches
0 conflicts
0x0eac7709…66c3
0x34b655…2a6f
2 touches
0 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
2 touches
0 conflicts
0x22effc8d…873c
0x34b655…2a6f
2 touches
0 conflicts
0x629f34ef…681a
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
3 conflicts on slot 0x1297819443…51d32f
Audit this contract →
← previous block·next block →recent activity