← previous blocknext block →recent activity
Analyzing
Block #91,017,183
18 transactions · 16 stateful · 2026-07-28 09:04:16 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,017,183 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w18w29w311w412w513w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x620b761c…270e
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x2aab0897…78f7
0x34b655…2a6f
6 touches
3 conflicts
0xb808b9ed…2865
0x34b655…2a6f
6 touches
3 conflicts
0xbbeac3b7…c14b
0x34b655…2a6f
6 touches
3 conflicts
0x2b0da3da…c9f3
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
15 conflicts on slot 0x620b761c50…c2270e
Audit this contract →
← previous block·next block →recent activity