← previous blocknext block →recent activity
Analyzing
Block #91,151,717
46 transactions · 41 stateful · 2026-07-28 20:21:13 UTC
Parallelism
63/100
Blocked
71%
Avg conflicts / tx
2.33
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #91,151,717 · 46 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w08w19w110w213w014w115w216w317w018w119w220w321w422w524w125w226w227w337w1038w1143w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x66a11a3b…0ee9
0xa6afd3…d132
8 touches
6 conflicts
0xb39cb1d8…effa
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x48cba2…b48b
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity