← previous blocknext block →recent activity
Analyzing
Block #75,846,998
61 transactions · 52 stateful · 2026-05-20 14:30:34 UTC
Parallelism
59/100
Blocked
79%
Avg conflicts / tx
5.18
Longest chain
25 deep
Execution timeline
did this block parallelize well?
view
block #75,846,998 · 61 txs across 25 waves · depth 25
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
wave w17
wave w18
wave w19
wave w20
wave w21
wave w22
wave w23
wave w24
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w822w952w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6417de0…2191
0xc8689a…ee79
40 touches
190 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
38 touches
171 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
34 touches
136 conflicts
0xd49762c9…1359
0x34b655…2a6f
34 touches
136 conflicts
0xf11f3c3f…1734
0x34b655…2a6f
34 touches
136 conflicts
0x908d4442…2c4b
0x34b655…2a6f
34 touches
136 conflicts
0x99f080dc…58c1
0x34b655…2a6f
32 touches
120 conflicts
0x0711ec2d…d973
0x34b655…2a6f
26 touches
78 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: 0xc8689a47…62ee79
190 conflicts on slot 0xc6417de023…802191
Audit this contract →
← previous block·next block →recent activity