← previous blocknext block →recent activity
Analyzing
Block #91,016,638
9 transactions · 9 stateful · 2026-07-28 09:01:32 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,016,638 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2b36ab5…39d8
0x34b655…2a6f
4 touches
1 conflict
0x4f394483…ff62
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
0x15eb6170…3da3
0x34b655…2a6f
2 touches
0 conflicts
0x207e9f25…4724
0x34b655…2a6f
2 touches
0 conflicts
0x207e9f25…4725
0x34b655…2a6f
2 touches
0 conflicts
0x223f6d48…a375
0x34b655…2a6f
2 touches
0 conflicts
0x42dfc6f5…844d
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xf2b36ab561…2e39d8
Audit this contract →
← previous block·next block →recent activity