← previous blocknext block →recent activity
Analyzing
Block #91,104,017
36 transactions · 32 stateful · 2026-07-28 16:21:15 UTC
Parallelism
56/100
Blocked
59%
Avg conflicts / tx
2.97
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #91,104,017 · 36 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
1w07w08w19w210w011w312w413w515w117w619w220w721w822w923w1024w1125w1226w1327w1428w1534w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
28 touches
91 conflicts
0xc824469a…6425
0x34b655…2a6f
26 touches
78 conflicts
0xbde524f4…43bf
0x34b655…2a6f
18 touches
36 conflicts
0x705ab4ae…0162
0x34b655…2a6f
18 touches
36 conflicts
0xd788486a…5370
0x34b655…2a6f
10 touches
10 conflicts
0x09a3eb75…0e1c
0x34b655…2a6f
9 touches
10 conflicts
0xb39cb1d8…effa
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
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
91 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity