← previous blocknext block →recent activity
Analyzing
Block #91,101,967
15 transactions · 14 stateful · 2026-07-28 16:10:56 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,101,967 · 15 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
2w03w04w06w111w112w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc58c80b…ff79
0x34b655…2a6f
8 touches
6 conflicts
0x0db8e93a…7dd1
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xcac5de58…5934
0x34b655…2a6f
6 touches
3 conflicts
0x5359bce1…be67
0x34b655…2a6f
4 touches
1 conflict
0x57998639…d04d
0x34b655…2a6f
4 touches
1 conflict
0x803cd43b…b348
0x34b655…2a6f
4 touches
1 conflict
0x9de538e5…7632
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
6 conflicts on slot 0xcc58c80b6c…80ff79
Audit this contract →
← previous block·next block →recent activity