← previous blocknext block →recent activity
Analyzing
Block #89,278,026
19 transactions · 18 stateful · 2026-07-21 20:24:44 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,278,026 · 19 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
5w07w010w111w012w113w214w315w217w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
8 touches
6 conflicts
0x6ffeb657…c789
0x0a2fbf…29b1
8 touches
6 conflicts
0x6ffeb657…c78a
0x0a2fbf…29b1
8 touches
6 conflicts
0x6ffeb657…c78d
0x0a2fbf…29b1
8 touches
6 conflicts
0x929825d6…7eeb
0x0a2fbf…29b1
8 touches
6 conflicts
0x929825d6…7eec
0x0a2fbf…29b1
8 touches
6 conflicts
0x00000000…0005
0x370e2e…63b4
8 touches
6 conflicts
0x464b4ac5…93fa
0x370e2e…63b4
8 touches
6 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
6 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity