← previous blocknext block →recent activity
Analyzing
Block #89,865,828
18 transactions · 15 stateful · 2026-07-24 08:10:59 UTC
Parallelism
78/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,865,828 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w110w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcbcc67c0…34de
0x34b655…2a6f
6 touches
3 conflicts
0xf18e384c…fda7
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7d02a2c5…9802
0x34b655…2a6f
4 touches
1 conflict
0x8f6a6bc7…5bd0
0x34b655…2a6f
4 touches
1 conflict
0xa51de3df…c65a
0x34b655…2a6f
4 touches
1 conflict
0xa86351b8…2c5a
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 0xcbcc67c0b7…8b34de
Audit this contract →
← previous block·next block →recent activity