← previous blocknext block →recent activity
Analyzing
Block #91,088,416
41 transactions · 40 stateful · 2026-07-28 15:02:44 UTC
Parallelism
61/100
Blocked
68%
Avg conflicts / tx
3.51
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #91,088,416 · 41 txs across 16 waves · depth 16
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
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w17w08w19w210w312w213w114w115w316w418w221w022w127w628w729w832w1138w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
32 touches
120 conflicts
0x737acb78…fce8
0x34b655…2a6f
24 touches
66 conflicts
0xce06a0f7…efef
0x34b655…2a6f
24 touches
66 conflicts
0xac2a0273…721b
0x34b655…2a6f
24 touches
66 conflicts
0xee039316…52a7
0x34b655…2a6f
12 touches
15 conflicts
0x07a56bac…27b3
0x34b655…2a6f
11 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 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
120 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity