← previous blocknext block →recent activity
Analyzing
Block #89,859,299
11 transactions · 11 stateful · 2026-07-24 07:38:08 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,859,299 · 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
1w02w03w19w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0xd5aacb43…f991
0x34b655…2a6f
6 touches
3 conflicts
0x8b501dcf…1040
0x34b655…2a6f
6 touches
3 conflicts
0xfb9f51f4…0f16
0x34b655…2a6f
4 touches
1 conflict
0x1cdfe548…d3aa
0x34b655…2a6f
4 touches
1 conflict
0x2c429f11…0652
0x34b655…2a6f
4 touches
1 conflict
0x476276f3…9765
0x34b655…2a6f
4 touches
1 conflict
0x522e20b4…fbc4
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 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity