← previous blocknext block →recent activity
Analyzing
Block #89,527,688
16 transactions · 14 stateful · 2026-07-23 00:13:09 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,527,688 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w17w28w09w110w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
10 touches
10 conflicts
0x1d489566…84cb
0x0a2fbf…29b1
10 touches
10 conflicts
0x1d489566…84cc
0x0a2fbf…29b1
10 touches
10 conflicts
0x1d489566…84cf
0x0a2fbf…29b1
10 touches
10 conflicts
0x55b4e430…44cb
0x754704…b603
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
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
10 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity