← previous blocknext block →recent activity
Analyzing
Block #89,567,162
14 transactions · 13 stateful · 2026-07-23 04:36:49 UTC
Parallelism
57/100
Blocked
54%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,567,162 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w07w18w29w111w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x75755da1…f498
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x06df379f…2653
0x34b655…2a6f
4 touches
1 conflict
0x07fdc70d…1976
0x34b655…2a6f
4 touches
1 conflict
0x1175233a…64e7
0x34b655…2a6f
4 touches
1 conflict
0x2b8d9898…d525
0x34b655…2a6f
4 touches
1 conflict
0x2c75ca93…a569
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
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 0x75755da170…b1f498
Audit this contract →
← previous block·next block →recent activity