← previous blocknext block →recent activity
Analyzing
Block #91,090,263
31 transactions · 30 stateful · 2026-07-28 15:12:01 UTC
Parallelism
58/100
Blocked
67%
Avg conflicts / tx
2.42
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #91,090,263 · 31 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w28w19w011w012w114w115w216w317w418w519w624w925w1027w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0x705ab4ae…0162
0x34b655…2a6f
12 touches
15 conflicts
0xe60f7d89…ddad
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x04be98f0…f405
0x34b655…2a6f
7 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
36 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity