← previous blocknext block →recent activity
Analyzing
Block #91,975,649
16 transactions · 14 stateful · 2026-07-31 17:28:27 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,975,649 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w07w19w211w212w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17935a8f…a796
0x34b655…2a6f
6 touches
3 conflicts
0x62f22aa6…40d4
0x34b655…2a6f
6 touches
3 conflicts
0x32409e80…a396
0x34b655…2a6f
6 touches
3 conflicts
0xae15115f…21af
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd70ab6b5…64cd
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
3 conflicts on slot 0x17935a8f01…66a796
Audit this contract →
← previous block·next block →recent activity