← previous blocknext block →recent activity
Analyzing
Block #91,111,158
18 transactions · 16 stateful · 2026-07-28 16:57:10 UTC
Parallelism
67/100
Blocked
31%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,111,158 · 18 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
1w02w19w213w314w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc58c80b…ff79
0x34b655…2a6f
12 touches
15 conflicts
0x729817ff…f2fd
0x34b655…2a6f
8 touches
6 conflicts
0x7b8eadca…ebca
0x34b655…2a6f
8 touches
6 conflicts
0x36a76bd2…1fb0
0x34b655…2a6f
6 touches
3 conflicts
0xdd9c5fda…e271
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x8fc481c4…6f66
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 0xcc58c80b6c…80ff79
Audit this contract →
← previous block·next block →recent activity