← previous blocknext block →recent activity
Analyzing
Block #89,698,324
13 transactions · 13 stateful · 2026-07-23 18:05:49 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,698,324 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w06w07w18w29w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89f9ad51…b081
0x0a2fbf…29b1
6 touches
3 conflicts
0x89f9ad51…b082
0x0a2fbf…29b1
6 touches
3 conflicts
0x89f9ad51…b085
0x0a2fbf…29b1
6 touches
3 conflicts
0xc91796b2…1217
0x0a2fbf…29b1
6 touches
3 conflicts
0x00000000…0005
0x370e2e…63b4
6 touches
3 conflicts
0xc91796b2…1218
0x0a2fbf…29b1
6 touches
3 conflicts
0x1bff683e…7ecb
0x754704…b603
6 touches
3 conflicts
0x55b4e430…44cb
0x754704…b603
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: 0x0a2fbf2d…f729b1
3 conflicts on slot 0x89f9ad5138…d4b081
Audit this contract →
← previous block·next block →recent activity