← previous blocknext block →recent activity
Analyzing
Block #91,190,057
30 transactions · 23 stateful · 2026-07-28 23:34:04 UTC
Parallelism
73/100
Blocked
57%
Avg conflicts / tx
0.8
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,190,057 · 30 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w15w27w08w115w218w319w420w321w524w226w627w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbc66586e…20fe
0x34b655…2a6f
8 touches
6 conflicts
0xefcdf197…96a2
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x8f3113c5…dbc4
0x34b655…2a6f
6 touches
3 conflicts
0x9f437213…eea4
0xd32edf…ff58
5 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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity