← previous blocknext block →recent activity
Analyzing
Block #91,959,253
35 transactions · 29 stateful · 2026-07-31 16:05:59 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.49
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,959,253 · 35 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
1w02w13w04w16w07w19w010w111w218w319w425w231w032w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0004
0x63e48b…53f2
6 touches
3 conflicts
0x818e1296…f4d7
0x34b655…2a6f
6 touches
3 conflicts
0x9157a62a…cf7a
0x34b655…2a6f
6 touches
3 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x63e48b…53f2
6 touches
3 conflicts
0x9a555477…19a8
0x754704…b603
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
10 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity