← previous blocknext block →recent activity
Analyzing
Block #89,526,502
16 transactions · 14 stateful · 2026-07-23 00:05:17 UTC
Parallelism
63/100
Blocked
36%
Avg conflicts / tx
0.44
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,526,502 · 16 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
4w06w08w110w211w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63da8263…7a24
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x25b30f61…63ce
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0x4ebf04a8…42e6
0x34b655…2a6f
4 touches
1 conflict
0x564e8dbe…da8a
0x34b655…2a6f
4 touches
1 conflict
0x564e8dbe…da8b
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 0x63da8263b5…587a24
Audit this contract →
← previous block·next block →recent activity