← previous blocknext block →recent activity
Analyzing
Block #75,990,555
40 transactions · 34 stateful · 2026-05-21 06:26:56 UTC
Parallelism
57/100
Blocked
79%
Avg conflicts / tx
4.4
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #75,990,555 · 40 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w29w010w111w212w313w415w616w717w818w919w1020w1122w1323w1424w1525w1626w328w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6417de0…2191
0xc8689a…ee79
30 touches
105 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
30 touches
105 conflicts
0x0711ec2d…d973
0x34b655…2a6f
22 touches
55 conflicts
0xd49762c9…1359
0x34b655…2a6f
22 touches
55 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
18 touches
36 conflicts
0x908d4442…2c4b
0x34b655…2a6f
18 touches
36 conflicts
0x99f080dc…58c1
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 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: Settlement / Helper
105 conflicts on slot 0xc6417de023…802191
Audit this contract →
← previous block·next block →recent activity