← previous blocknext block →recent activity
Analyzing
Block #91,423,100
21 transactions · 18 stateful · 2026-07-29 19:07:51 UTC
Parallelism
71/100
Blocked
61%
Avg conflicts / tx
1.29
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,423,100 · 21 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
1w02w13w24w35w16w07w112w413w214w315w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xfd42a6b9…4c81
0x34b655…2a6f
10 touches
10 conflicts
0x8c556eda…99df
0xd32edf…ff58
9 touches
10 conflicts
0xf862728a…c2bf
0x34b655…2a6f
8 touches
6 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x2c2db8e9…fdc7
0x34b655…2a6f
4 touches
1 conflict
0x6119ad89…63fe
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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity