← previous blocknext block →recent activity
Analyzing
Block #91,129,129
8 transactions · 8 stateful · 2026-07-28 18:27:34 UTC
Parallelism
38/100
Blocked
50%
Avg conflicts / tx
1.13
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,129,129 · 8 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
1w03w14w25w36w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ffb6fe7…ddc7
0x34b655…2a6f
8 touches
6 conflicts
0x361f4a1b…1f14
0x34b655…2a6f
6 touches
3 conflicts
0x38c6ff01…689f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x43e15ca4…039d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xf4ff6e8d…0427
0x34b655…2a6f
4 touches
1 conflict
0x0802d0d8…dd0c
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
6 conflicts on slot 0x6ffb6fe758…f2ddc7
Audit this contract →
← previous block·next block →recent activity