← previous blocknext block →recent activity
Analyzing
Block #89,688,962
11 transactions · 11 stateful · 2026-07-23 17:18:37 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,688,962 · 11 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
2w05w18w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e0e8837…2e59
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0x89c4fedf…b214
0x34b655…2a6f
4 touches
1 conflict
0x89c4fedf…b215
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x00bbd28c…e227
0x34b655…2a6f
4 touches
1 conflict
0xdb89ef9a…606c
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 0x6e0e883716…732e59
Audit this contract →
← previous block·next block →recent activity