← previous blocknext block →recent activity
Analyzing
Block #89,570,682
24 transactions · 22 stateful · 2026-07-23 05:00:24 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
1.21
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #89,570,682 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w110w011w112w213w314w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
16 touches
28 conflicts
0x74266552…4f79
0x0a2fbf…29b1
16 touches
28 conflicts
0x74266552…4f7a
0x0a2fbf…29b1
16 touches
28 conflicts
0x7d5b9adc…589e
0x0a2fbf…29b1
16 touches
28 conflicts
0x7d5b9adc…589f
0x0a2fbf…29b1
16 touches
28 conflicts
0x7d5b9adc…58a2
0x0a2fbf…29b1
16 touches
28 conflicts
0x00000000…0005
0x370e2e…63b4
16 touches
28 conflicts
0x1bff683e…7ecb
0x754704…b603
16 touches
28 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: 0x0a2fbf2d…f729b1
28 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity