← previous blocknext block →recent activity
Analyzing
Block #91,073,229
34 transactions · 31 stateful · 2026-07-28 13:46:16 UTC
Parallelism
59/100
Blocked
68%
Avg conflicts / tx
2.09
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #91,073,229 · 34 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w18w29w010w111w212w013w115w216w317w419w220w521w325w626w728w829w930w1033w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x08a39015…efa0
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x2533f477…a43b
0x34b655…2a6f
8 touches
6 conflicts
0x9a7be229…5108
0x34b655…2a6f
8 touches
6 conflicts
0x1321736a…43e3
0x34b655…2a6f
8 touches
6 conflicts
0xda2ee2e7…968a
0x34b655…2a6f
8 touches
6 conflicts
0xf5a82f09…3070
0x34b655…2a6f
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: Perpl
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity