← previous blocknext block →recent activity
Analyzing
Block #91,954,281
11 transactions · 11 stateful · 2026-07-31 15:40:59 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,954,281 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w27w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe17f641…9633
0x34b655…2a6f
6 touches
3 conflicts
0xc44c765a…244e
0x7b9256…1fb2
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
4 touches
1 conflict
0x02eef19d…c4f1
0x7b9256…1fb2
4 touches
1 conflict
0x02eef19d…c4f2
0x7b9256…1fb2
4 touches
1 conflict
0x02eef19d…c4f5
0x7b9256…1fb2
4 touches
1 conflict
0xc44c765a…244d
0x7b9256…1fb2
4 touches
1 conflict
0x0eac7709…66c3
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 0xbe17f64164…b19633
Audit this contract →
← previous block·next block →recent activity