← previous blocknext block →recent activity
Analyzing
Block #76,465,289
47 transactions · 44 stateful · 2026-05-23 11:08:43 UTC
Parallelism
62/100
Blocked
75%
Avg conflicts / tx
4.21
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #76,465,289 · 47 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
1w02w13w04w05w07w18w29w310w411w512w614w725w826w930w931w1032w1133w1234w1335w1436w1537w1638w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3afb222…4d17
0xa6afd3…d132
32 touches
120 conflicts
0x00000000…003d
0xa6afd3…d132
30 touches
105 conflicts
0x99a21305…dffc
0x2a68ba…90c5
30 touches
105 conflicts
0x99a4d286…ad43
0xa6afd3…d132
28 touches
91 conflicts
0xea7ebe9d…709e
0x1d1325…2305
26 touches
78 conflicts
0x10abefc9…c9bc
0x1d1325…2305
26 touches
78 conflicts
0x10d80fee…dbda
0x1d1325…2305
26 touches
78 conflicts
0x3484c9df…bfd5
0x1d1325…2305
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: 0xa6afd386…b0d132
120 conflicts on slot 0xc3afb2229f…7f4d17
Audit this contract →
← previous block·next block →recent activity