← previous blocknext block →recent activity
Analyzing
Block #89,528,380
17 transactions · 16 stateful · 2026-07-23 00:17:46 UTC
Parallelism
71/100
Blocked
56%
Avg conflicts / tx
1.12
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,528,380 · 17 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
4w05w16w27w19w310w412w114w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc78e5ff5…99b9
0x34b655…2a6f
8 touches
6 conflicts
0xf609f09b…f03a
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xf4c9a0df…dcd4
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x7f06125e…4bb7
0x34b655…2a6f
6 touches
3 conflicts
0xadccdabf…b8a6
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 0xc78e5ff563…d899b9
Audit this contract →
← previous block·next block →recent activity