← previous blocknext block →recent activity
Analyzing
Block #91,089,138
40 transactions · 37 stateful · 2026-07-28 15:06:22 UTC
Parallelism
85/100
Blocked
59%
Avg conflicts / tx
1.43
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,089,138 · 40 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
1w02w13w04w05w16w27w38w49w010w111w212w313w422w127w228w531w332w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
12 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xffa7d0a4…b10a
0x40c49f…2af0
8 touches
6 conflicts
0xc782ec05…5bb2
0xa6afd3…d132
8 touches
6 conflicts
0x342fbbca…d443
0x40c49f…2af0
8 touches
6 conflicts
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: 0x48cba278…e2b48b
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity