← previous blocknext block →recent activity
Analyzing
Block #76,550,758
60 transactions · 50 stateful · 2026-05-23 20:37:57 UTC
Parallelism
70/100
Blocked
74%
Avg conflicts / tx
3.7
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #76,550,758 · 60 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
1w02w13w24w35w46w57w68w79w820w821w922w1023w1125w1226w1331w1432w1552w1653w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
28 touches
91 conflicts
0x99a21305…dffc
0x2a68ba…90c5
26 touches
78 conflicts
0x2dc020c7…0697
0xc8689a…ee79
22 touches
55 conflicts
0x00000000…003d
0xa6afd3…d132
22 touches
55 conflicts
0xac2a0273…721b
0x34b655…2a6f
22 touches
55 conflicts
0xafd59af5…5257
0xc8689a…ee79
20 touches
45 conflicts
0x43676b64…6276
0x34b655…2a6f
20 touches
45 conflicts
0x921a58d1…db22
0x34b655…2a6f
20 touches
45 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
91 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity