← previous blocknext block →recent activity
Analyzing
Block #91,147,328
15 transactions · 14 stateful · 2026-07-28 19:59:08 UTC
Parallelism
40/100
Blocked
57%
Avg conflicts / tx
2.4
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #91,147,328 · 15 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w410w511w612w713w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce06a0f7…efef
0x34b655…2a6f
18 touches
36 conflicts
0xbde524f4…43bf
0x34b655…2a6f
18 touches
36 conflicts
0xac2a0273…721b
0x34b655…2a6f
18 touches
36 conflicts
0x737acb78…fce8
0x34b655…2a6f
18 touches
36 conflicts
0xfd3ab355…9d24
0x34b655…2a6f
9 touches
10 conflicts
0x5a884e80…ed8a
0x34b655…2a6f
8 touches
6 conflicts
0xe5a77819…e5d5
0x34b655…2a6f
7 touches
6 conflicts
0x3ac06bf5…9424
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
36 conflicts on slot 0xce06a0f7c4…61efef
Audit this contract →
← previous block·next block →recent activity