← previous blocknext block →recent activity
Analyzing
Block #73,478,959
35 transactions · 30 stateful · 2026-05-09 14:51:19 UTC
Parallelism
54/100
Blocked
77%
Avg conflicts / tx
2.57
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #73,478,959 · 35 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
1w02w13w24w05w26w07w18w212w113w014w115w216w317w418w519w620w721w824w125w132w1334w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa91c899f…6ee3
0x34b655…2a6f
18 touches
36 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
18 touches
36 conflicts
0x1acaa26f…7b77
0x34b655…2a6f
16 touches
28 conflicts
0xc6417de0…2191
0xc8689a…ee79
14 touches
21 conflicts
0x57de3828…3fbb
0x34b655…2a6f
14 touches
21 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
14 touches
21 conflicts
0x908d4442…2c4b
0x34b655…2a6f
14 touches
21 conflicts
0x99f080dc…58c1
0x34b655…2a6f
14 touches
21 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
36 conflicts on slot 0xa91c899f02…fa6ee3
Audit this contract →
← previous block·next block →recent activity