← previous blocknext block →recent activity
Analyzing
Block #91,131,797
20 transactions · 17 stateful · 2026-07-28 18:40:59 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,131,797 · 20 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
1w04w15w26w38w49w511w012w113w015w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa779293b…5e59
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x61f9677a…89f2
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x418f6232…2de6
0x34b655…2a6f
4 touches
1 conflict
0x71b813c8…4a17
0x34b655…2a6f
4 touches
1 conflict
0x9d9b2e40…6d8e
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 0xa779293bef…815e59
Audit this contract →
← previous block·next block →recent activity