← previous blocknext block →recent activity
Analyzing
Block #91,262,086
24 transactions · 20 stateful · 2026-07-29 05:36:30 UTC
Parallelism
79/100
Blocked
40%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,262,086 · 24 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
5w06w17w08w111w012w213w315w417w121w022w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd30f9e74…d404
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd52424b6…774c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
6 touches
3 conflicts
0xca4542ce…bdb2
0x065c9d…c394
4 touches
1 conflict
0xc0164b20…4db5
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity