← previous blocknext block →recent activity
Analyzing
Block #91,417,322
32 transactions · 21 stateful · 2026-07-29 18:38:47 UTC
Parallelism
78/100
Blocked
48%
Avg conflicts / tx
0.56
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,417,322 · 32 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
13w014w115w216w317w418w019w520w021w123w127w528w629w030w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x1bf8d2af…d140
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xefcdf197…96a2
0x34b655…2a6f
4 touches
1 conflict
0xf9e23360…8ef7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x3a6aab02…1436
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity