← previous blocknext block →recent activity
Analyzing
Block #91,013,464
15 transactions · 14 stateful · 2026-07-28 08:45:34 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,013,464 · 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
1w02w13w25w36w410w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf831072…51d5
0x80f006…d585
8 touches
6 conflicts
0xaf831072…51d6
0x80f006…d585
8 touches
6 conflicts
0x00000000…0004
0x8d5c2d…f642
8 touches
6 conflicts
0xbb371eab…3efc
0x8d5c2d…f642
8 touches
6 conflicts
0xa8669ab5…6af7
0x754704…b603
8 touches
6 conflicts
0xb4075714…71fa
0xba1333…9ba9
8 touches
6 conflicts
0xb816a323…1256
0xba1333…9ba9
8 touches
6 conflicts
0xca109069…8b94
0xba1333…9ba9
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: 0x80f00661…45d585
6 conflicts on slot 0xaf831072f6…c551d5
Audit this contract →
← previous block·next block →recent activity