← previous blocknext block →recent activity
Analyzing
Block #75,198,919
52 transactions · 39 stateful · 2026-05-17 14:16:09 UTC
Parallelism
65/100
Blocked
77%
Avg conflicts / tx
3.17
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #75,198,919 · 52 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w26w07w113w114w215w016w321w022w123w224w325w426w527w628w729w838w339w340w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
26 touches
78 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x3e49348b…9445
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0xafd59af5…5257
0xc8689a…ee79
10 touches
10 conflicts
0x10f5f4d8…572e
0x34b655…2a6f
10 touches
10 conflicts
0x20ac0567…c954
0x34b655…2a6f
10 touches
10 conflicts
0x2484cc15…5afc
0x34b655…2a6f
10 touches
10 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
78 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity