← previous blocknext block →recent activity
Analyzing
Block #91,151,613
20 transactions · 19 stateful · 2026-07-28 20:20:41 UTC
Parallelism
60/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,151,613 · 20 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
1w02w16w07w28w39w410w511w012w114w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x41891af2…ed2a
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xb39cb1d8…effa
0x34b655…2a6f
8 touches
6 conflicts
0x4f394483…ff62
0x34b655…2a6f
6 touches
3 conflicts
0x0efc210e…70ab
0x34b655…2a6f
6 touches
3 conflicts
0x784eaad2…d176
0x34b655…2a6f
6 touches
3 conflicts
0xefefea9b…815c
0x34b655…2a6f
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity