← previous blocknext block →recent activity
Analyzing
Block #91,292,038
12 transactions · 11 stateful · 2026-07-29 08:07:58 UTC
Parallelism
42/100
Blocked
64%
Avg conflicts / tx
1.75
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,292,038 · 12 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w47w58w610w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c390858…b1ed
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xfb120845…7ae2
0x34b655…2a6f
10 touches
10 conflicts
0x25da5e59…fee6
0x34b655…2a6f
6 touches
3 conflicts
0x50c0dd87…1128
0x34b655…2a6f
6 touches
3 conflicts
0x681cc0ee…eb83
0x34b655…2a6f
6 touches
3 conflicts
0x7d6b9af1…9a38
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 0x2c3908588c…50b1ed
Audit this contract →
← previous block·next block →recent activity