← previous blocknext block →recent activity
Analyzing
Block #88,350,879
20 transactions · 18 stateful · 2026-07-17 13:03:23 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,350,879 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w19w010w011w112w213w214w115w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
6 touches
3 conflicts
0x2010299d…6c9b
0x0a2fbf…29b1
6 touches
3 conflicts
0x2010299d…6c9c
0x0a2fbf…29b1
6 touches
3 conflicts
0x2010299d…6c9f
0x0a2fbf…29b1
6 touches
3 conflicts
0x3bbcd95b…3d86
0x0a2fbf…29b1
6 touches
3 conflicts
0x3bbcd95b…3d87
0x0a2fbf…29b1
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
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 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity