← previous blocknext block →recent activity
Analyzing
Block #89,692,508
18 transactions · 17 stateful · 2026-07-23 17:36:30 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.72
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,692,508 · 18 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
4w05w06w17w29w310w011w112w213w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x837e3e81…8087
0x0a2fbf…29b1
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x837e3e81…8088
0x0a2fbf…29b1
8 touches
6 conflicts
0x00000000…0005
0x370e2e…63b4
8 touches
6 conflicts
0x00000000…0006
0x0a2fbf…29b1
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x8c006ca6…d25e
0x0a2fbf…29b1
8 touches
6 conflicts
0x8c006ca6…d25f
0x0a2fbf…29b1
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 0x837e3e81ff…a98087
Audit this contract →
← previous block·next block →recent activity