← previous blocknext block →recent activity
Analyzing
Block #89,872,956
15 transactions · 15 stateful · 2026-07-24 08:46:50 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,872,956 · 15 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
2w03w16w07w18w29w310w411w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0005
0x370e2e…63b4
10 touches
10 conflicts
0xabc88785…c97b
0x0a2fbf…29b1
10 touches
10 conflicts
0xabc88785…c97e
0x0a2fbf…29b1
10 touches
10 conflicts
0xb314615f…4c13
0x0a2fbf…29b1
10 touches
10 conflicts
0xb314615f…4c14
0x0a2fbf…29b1
10 touches
10 conflicts
0x00000000…0006
0x0a2fbf…29b1
10 touches
10 conflicts
0xabc88785…c97a
0x0a2fbf…29b1
10 touches
10 conflicts
0x1bff683e…7ecb
0x754704…b603
10 touches
10 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: 0x370e2ee6…bd63b4
10 conflicts on slot 0x0000000000…000005
Audit this contract →
← previous block·next block →recent activity