← previous blocknext block →recent activity
Analyzing
Block #91,271,829
71 transactions · 58 stateful · 2026-07-29 06:26:12 UTC
Parallelism
66/100
Blocked
76%
Avg conflicts / tx
3.31
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #91,271,829 · 71 txs across 24 waves · depth 24
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
wave w17
wave w18
wave w19
wave w20
wave w21
wave w22
wave w23
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w09w110w211w312w413w514w615w742w548w950w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
26 touches
78 conflicts
0x889d5e90…929a
0x2a68ba…90c5
16 touches
28 conflicts
0xf4f9cac7…fd98
0x34b655…2a6f
14 touches
21 conflicts
0x103be197…826c
0xa6afd3…d132
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x306233f2…96c3
0x34b655…2a6f
14 touches
21 conflicts
0xebac0f82…a49c
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
14 touches
21 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
78 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity