← previous blocknext block →recent activity
Analyzing
Block #91,162,312
24 transactions · 23 stateful · 2026-07-28 21:14:29 UTC
Parallelism
58/100
Blocked
52%
Avg conflicts / tx
1.67
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #91,162,312 · 24 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w07w38w410w511w612w716w817w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x564b7fcf…deb4
0x34b655…2a6f
10 touches
10 conflicts
0x5502e1cc…3910
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x0a0cecef…4ed0
0x34b655…2a6f
6 touches
3 conflicts
0x4bc1abab…5874
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity