← previous blocknext block →recent activity
Analyzing
Block #91,417,881
31 transactions · 24 stateful · 2026-07-29 18:41:36 UTC
Parallelism
65/100
Blocked
58%
Avg conflicts / tx
1.29
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #91,417,881 · 31 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
5w06w111w012w113w214w315w417w218w519w620w223w624w727w828w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbed5ddf9…d1d2
0x34b655…2a6f
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xc0eb79d1…29a4
0x34b655…2a6f
8 touches
6 conflicts
0xb9834665…e363
0x34b655…2a6f
8 touches
6 conflicts
0xfecb18c0…01ed
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x1ebb35bb…ef2a
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 0xbed5ddf9d3…36d1d2
Audit this contract →
← previous block·next block →recent activity