← previous blocknext block →recent activity
Analyzing
Block #91,111,128
27 transactions · 26 stateful · 2026-07-28 16:57:01 UTC
Parallelism
63/100
Blocked
46%
Avg conflicts / tx
1.33
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #91,111,128 · 27 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
1w03w04w111w112w013w115w216w317w418w519w620w723w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
16 touches
28 conflicts
0x4bc1abab…5874
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0xf3d10975…0d07
0x34b655…2a6f
12 touches
15 conflicts
0x217bd767…b79e
0x34b655…2a6f
10 touches
10 conflicts
0x1c3c9acb…e2b0
0x34b655…2a6f
9 touches
10 conflicts
0x13df3104…acef
0x34b655…2a6f
8 touches
6 conflicts
0x01257dfc…ce9a
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
28 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity