← previous blocknext block →recent activity
Analyzing
Block #89,402,475
22 transactions · 20 stateful · 2026-07-22 10:16:34 UTC
Parallelism
77/100
Blocked
50%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,402,475 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w28w09w112w213w114w215w316w417w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x521553ff…d548
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x27034002…2f27
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x5aae2be3…b780
0x34b655…2a6f
4 touches
1 conflict
0x620d4d3d…1735
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 0x521553ff41…c5d548
Audit this contract →
← previous block·next block →recent activity