← previous blocknext block →recent activity
Analyzing
Block #76,482,042
43 transactions · 39 stateful · 2026-05-23 13:00:21 UTC
Parallelism
56/100
Blocked
74%
Avg conflicts / tx
4.28
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #76,482,042 · 43 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w08w19w211w012w114w115w216w317w418w519w628w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c913164…5c2e
0x34b655…2a6f
32 touches
120 conflicts
0xf853eb8e…4027
0x34b655…2a6f
32 touches
120 conflicts
0xc6417de0…2191
0xc8689a…ee79
28 touches
91 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
28 touches
91 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
26 touches
78 conflicts
0x9cc607d0…c9c7
0x34b655…2a6f
26 touches
78 conflicts
0x4a6c9758…b036
0x34b655…2a6f
18 touches
36 conflicts
0xa23e4e28…e875
0x34b655…2a6f
18 touches
36 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
120 conflicts on slot 0x1c913164f5…845c2e
Audit this contract →
← previous block·next block →recent activity