← previous blocknext block →recent activity
Analyzing
Block #91,435,346
32 transactions · 29 stateful · 2026-07-29 20:10:21 UTC
Parallelism
66/100
Blocked
45%
Avg conflicts / tx
1.63
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #91,435,346 · 32 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w210w011w112w214w315w416w517w618w726w927w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…00c9
0x34b655…2a6f
10 touches
10 conflicts
0xda2ee2e7…968a
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbd96f96f…5843
0x34b655…2a6f
8 touches
6 conflicts
0x42d5e8f3…5930
0x34b655…2a6f
6 touches
3 conflicts
0xe2ca9bf2…8da8
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: Perpl
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity