← previous blocknext block →recent activity
Analyzing
Block #89,518,609
29 transactions · 24 stateful · 2026-07-22 23:12:30 UTC
Parallelism
72/100
Blocked
46%
Avg conflicts / tx
1.24
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #89,518,609 · 29 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
2w03w18w09w110w211w312w413w514w620w322w724w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x6bfc7921…ffc8
0x34b655…2a6f
6 touches
3 conflicts
0xb26fce3e…f47f
0x34b655…2a6f
6 touches
3 conflicts
0x21321ef8…bd04
0x34b655…2a6f
4 touches
1 conflict
0x2c2761c0…476e
0x34b655…2a6f
4 touches
1 conflict
0x4abfb389…18f4
0x34b655…2a6f
4 touches
1 conflict
0x5f81aed7…49ff
0x34b655…2a6f
4 touches
1 conflict
0x70e3da66…674a
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity