← previous blocknext block →recent activity
Analyzing
Block #91,408,133
16 transactions · 15 stateful · 2026-07-29 17:52:25 UTC
Parallelism
44/100
Blocked
53%
Avg conflicts / tx
0.94
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #91,408,133 · 16 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w410w512w613w714w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xc0eb79d1…29a4
0x34b655…2a6f
6 touches
3 conflicts
0xfbe6a366…8ca1
0x34b655…2a6f
4 touches
1 conflict
0x2c66ecd1…f41d
0x34b655…2a6f
4 touches
1 conflict
0x4e068769…91ad
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity