← previous blocknext block →recent activity
Analyzing
Block #91,097,207
25 transactions · 24 stateful · 2026-07-28 15:46:59 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,097,207 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w08w19w210w011w112w213w315w417w318w419w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0x5e4b65e1…ebe1
0x34b655…2a6f
4 touches
1 conflict
0x6f15256f…5550
0x34b655…2a6f
4 touches
1 conflict
0x709424ea…671e
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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