← previous blocknext block →recent activity
Analyzing
Block #91,105,447
19 transactions · 18 stateful · 2026-07-28 16:28:26 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,105,447 · 19 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
1w04w05w16w27w08w19w210w111w212w115w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x309ce4a6…d326
0x34b655…2a6f
4 touches
1 conflict
0x329f2f7d…dcff
0x34b655…2a6f
4 touches
1 conflict
0x3a996b35…bc8f
0x34b655…2a6f
4 touches
1 conflict
0x456150d1…09f3
0x34b655…2a6f
4 touches
1 conflict
0x4a6b3039…6a98
0x34b655…2a6f
4 touches
1 conflict
0x61589664…4bd6
0x34b655…2a6f
4 touches
1 conflict
0x6f6b4878…d72d
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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity