← previous blocknext block →recent activity
Analyzing
Block #91,406,291
15 transactions · 14 stateful · 2026-07-29 17:43:05 UTC
Parallelism
60/100
Blocked
43%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,406,291 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w28w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5899760…c130
0x34b655…2a6f
6 touches
3 conflicts
0xb852cf41…12b6
0x34b655…2a6f
5 touches
3 conflicts
0x3601aa45…29cb
0x34b655…2a6f
4 touches
1 conflict
0x39146670…bc53
0x34b655…2a6f
4 touches
1 conflict
0x3cb231a9…887d
0x34b655…2a6f
4 touches
1 conflict
0x3dc8ed8f…9df1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x491a4dea…160e
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 0xf58997607e…2ec130
Audit this contract →
← previous block·next block →recent activity