← previous blocknext block →recent activity
Analyzing
Block #89,596,471
23 transactions · 20 stateful · 2026-07-23 07:52:32 UTC
Parallelism
74/100
Blocked
40%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,596,471 · 23 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
6w07w09w110w211w312w414w016w517w120w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x1bf8d2af…d140
0x34b655…2a6f
6 touches
3 conflicts
0x324ec4d3…f156
0x34b655…2a6f
6 touches
3 conflicts
0x34413116…952e
0x34b655…2a6f
6 touches
3 conflicts
0xaa9f27b0…9cf2
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe2933bc0…d0d2
0x34b655…2a6f
6 touches
3 conflicts
0x4360b49f…140d
0x34b655…2a6f
6 touches
3 conflicts
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity