← previous blocknext block →recent activity
Analyzing
Block #91,411,573
31 transactions · 27 stateful · 2026-07-29 18:09:52 UTC
Parallelism
65/100
Blocked
67%
Avg conflicts / tx
2.19
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #91,411,573 · 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
3w04w15w26w37w48w510w011w112w013w114w215w317w418w521w623w625w726w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9834665…e363
0x34b655…2a6f
12 touches
15 conflicts
0xfa5faaa9…9f7d
0xd32edf…ff58
11 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x5502e1cc…3910
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x5fe7e126…6dd2
0x34b655…2a6f
8 touches
6 conflicts
0xbed5ddf9…d1d2
0x34b655…2a6f
8 touches
6 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 0xb983466539…cee363
Audit this contract →
← previous block·next block →recent activity