← previous blocknext block →recent activity
Analyzing
Block #91,077,859
17 transactions · 15 stateful · 2026-07-28 14:09:36 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,077,859 · 17 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
1w02w13w24w38w09w111w212w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbdc80bf7…e947
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x614f2962…6393
0x34b655…2a6f
6 touches
3 conflicts
0x5a409e7f…09b6
0x2b46c0…1669
4 touches
1 conflict
0x62811193…1868
0x2b46c0…1669
4 touches
1 conflict
0x62811193…1869
0x2b46c0…1669
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
10 conflicts on slot 0xbdc80bf733…aae947
Audit this contract →
← previous block·next block →recent activity