← previous blocknext block →recent activity
Analyzing
Block #91,109,858
33 transactions · 29 stateful · 2026-07-28 16:50:38 UTC
Parallelism
85/100
Blocked
62%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,109,858 · 33 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
1w02w13w14w26w07w18w19w210w111w213w217w018w119w220w322w324w328w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x6b666228…f308
0xd32edf…ff58
7 touches
6 conflicts
0x9ba7d0c8…ec52
0xee8c0e…1242
6 touches
3 conflicts
0x00000000…0001
0x354d92…66fb
6 touches
3 conflicts
0x38b5b2ce…c5bb
0x354d92…66fb
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0xdb9f7f76…18c9
0x754704…b603
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
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: Perpl
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity