← previous blocknext block →recent activity
Analyzing
Block #89,518,745
19 transactions · 18 stateful · 2026-07-22 23:13:25 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,518,745 · 19 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
1w02w13w04w17w28w310w411w214w215w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ad18e06…472a
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x181ad9cf…26f4
0x34b655…2a6f
4 touches
1 conflict
0x41377979…0a18
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6b76ce29…0e84
0x34b655…2a6f
4 touches
1 conflict
0x6bfc7921…ffc8
0x34b655…2a6f
4 touches
1 conflict
0x9ad325f5…cc43
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 0x8ad18e06e0…88472a
Audit this contract →
← previous block·next block →recent activity