← previous blocknext block →recent activity
Analyzing
Block #75,198,780
59 transactions · 48 stateful · 2026-05-17 14:15:14 UTC
Parallelism
61/100
Blocked
77%
Avg conflicts / tx
4.02
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #75,198,780 · 59 txs across 23 waves · depth 23
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w27w08w112w313w414w515w616w739w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
30 touches
105 conflicts
0xc6417de0…2191
0xc8689a…ee79
18 touches
36 conflicts
0x0711ec2d…d973
0x34b655…2a6f
18 touches
36 conflicts
0xd159b6e7…5cfb
0x34b655…2a6f
18 touches
36 conflicts
0x4f483049…3cc7
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xd49762c9…1359
0x34b655…2a6f
18 touches
36 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
16 touches
28 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
105 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity