← previous blocknext block →recent activity
Analyzing
Block #91,235,357
19 transactions · 18 stateful · 2026-07-29 03:21:56 UTC
Parallelism
79/100
Blocked
22%
Avg conflicts / tx
0.32
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,235,357 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w111w214w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb66e4903…7e80
0x34b655…2a6f
6 touches
3 conflicts
0x9a287655…f785
0x34b655…2a6f
6 touches
3 conflicts
0x1af644dc…0822
0x34b655…2a6f
4 touches
1 conflict
0x259ed0cc…bef9
0x34b655…2a6f
4 touches
1 conflict
0x259ed0cc…befa
0x34b655…2a6f
4 touches
1 conflict
0x324cb18b…bcc6
0x34b655…2a6f
4 touches
1 conflict
0x36890fff…f3d1
0x34b655…2a6f
4 touches
1 conflict
0x3a996b35…bc8f
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
3 conflicts on slot 0xb66e490333…f07e80
Audit this contract →
← previous block·next block →recent activity