← previous blocknext block →recent activity
Analyzing
Block #91,408,476
40 transactions · 37 stateful · 2026-07-29 17:54:10 UTC
Parallelism
60/100
Blocked
59%
Avg conflicts / tx
2.83
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #91,408,476 · 40 txs across 16 waves · depth 16
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
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w09w010w111w212w313w415w516w618w219w225w728w1029w1132w1233w1334w1435w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0xac3e4969…39e9
0x34b655…2a6f
20 touches
45 conflicts
0xbbeac3b7…c14b
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc0eb79d1…29a4
0x34b655…2a6f
10 touches
10 conflicts
0xf9e23360…8ef7
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
45 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity