← previous blocknext block →recent activity
Analyzing
Block #89,863,328
10 transactions · 10 stateful · 2026-07-24 07:58:24 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,863,328 · 10 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
2w04w15w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c1ca157…f583
0x0a2fbf…29b1
6 touches
3 conflicts
0x0c1ca157…f584
0x0a2fbf…29b1
6 touches
3 conflicts
0x00000000…0005
0x370e2e…63b4
6 touches
3 conflicts
0xcd32ca3e…c011
0x370e2e…63b4
6 touches
3 conflicts
0x0c1ca157…f587
0x0a2fbf…29b1
6 touches
3 conflicts
0x1bff683e…7ecb
0x754704…b603
6 touches
3 conflicts
0x55b4e430…44cb
0x754704…b603
6 touches
3 conflicts
0x1d2d4004…6722
0x0a2fbf…29b1
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 0x0c1ca15717…9df583
Audit this contract →
← previous block·next block →recent activity