← previous blocknext block →recent activity
Analyzing
Block #89,414,170
17 transactions · 16 stateful · 2026-07-22 11:34:45 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.12
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,414,170 · 17 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
5w06w17w08w19w210w311w412w113w214w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee6bd99e…3f6e
0x0a2fbf…29b1
12 touches
15 conflicts
0xee6bd99e…3f6f
0x0a2fbf…29b1
12 touches
15 conflicts
0xee6bd99e…3f72
0x0a2fbf…29b1
12 touches
15 conflicts
0x55b4e430…44cb
0x754704…b603
12 touches
15 conflicts
0x00000000…0006
0x0a2fbf…29b1
12 touches
15 conflicts
0xc87d291b…043b
0x0a2fbf…29b1
10 touches
10 conflicts
0x00000000…0005
0x370e2e…63b4
10 touches
10 conflicts
0xc87d291b…043a
0x0a2fbf…29b1
10 touches
10 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
15 conflicts on slot 0xee6bd99ee7…713f6e
Audit this contract →
← previous block·next block →recent activity