← previous blocknext block →recent activity
Analyzing
Block #91,008,266
11 transactions · 11 stateful · 2026-07-28 08:19:18 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.73
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,008,266 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w15w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e6b8ec7…2197
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd0391486…43b7
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x390b2068…fc14
0x34b655…2a6f
4 touches
1 conflict
0x42131e2c…ae3c
0x34b655…2a6f
4 touches
1 conflict
0x43a02937…4672
0x34b655…2a6f
4 touches
1 conflict
0x442e26a3…e968
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x6e6b8ec76e…cb2197
Audit this contract →
← previous block·next block →recent activity