← previous blocknext block →recent activity
Analyzing
Block #89,737,294
11 transactions · 10 stateful · 2026-07-23 21:22:29 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,737,294 · 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
1w02w16w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e162301…9c1b
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xf2f4727d…cdb7
0x34b655…2a6f
4 touches
1 conflict
0x08b17df7…f039
0x34b655…2a6f
2 touches
0 conflicts
0x15e0dca8…c542
0x34b655…2a6f
2 touches
0 conflicts
0x33967383…de4d
0x34b655…2a6f
2 touches
0 conflicts
0x4e2af3ce…caf3
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x7e1623011b…ce9c1b
Audit this contract →
← previous block·next block →recent activity