← previous blocknext block →recent activity
Analyzing
Block #91,110,127
22 transactions · 20 stateful · 2026-07-28 16:51:59 UTC
Parallelism
50/100
Blocked
55%
Avg conflicts / tx
2.27
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #91,110,127 · 22 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w19w110w211w312w413w514w615w716w817w918w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
20 touches
45 conflicts
0x737acb78…fce8
0x34b655…2a6f
18 touches
36 conflicts
0xac2a0273…721b
0x34b655…2a6f
18 touches
36 conflicts
0xce06a0f7…efef
0x34b655…2a6f
18 touches
36 conflicts
0x13df3104…acef
0x34b655…2a6f
9 touches
10 conflicts
0x4f024493…baf5
0x34b655…2a6f
9 touches
10 conflicts
0x5c16527f…628c
0x34b655…2a6f
8 touches
6 conflicts
0xd6549c4a…c006
0x34b655…2a6f
7 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
45 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity