← previous blocknext block →recent activity
Analyzing
Block #76,550,775
76 transactions · 54 stateful · 2026-05-23 20:38:04 UTC
Parallelism
76/100
Blocked
74%
Avg conflicts / tx
2.57
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #76,550,775 · 76 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
1w02w13w24w35w46w519w425w126w227w329w632w733w834w935w1037w1138w1239w1340w1441w1542w1643w1746w1447w1566w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
26 touches
78 conflicts
0xe2e94dfa…5026
0x2a68ba…90c5
26 touches
78 conflicts
0x222fc893…acc9
0xa6afd3…d132
26 touches
78 conflicts
0x99a21305…dffc
0x2a68ba…90c5
24 touches
66 conflicts
0x10d80fee…dbda
0x1d1325…2305
24 touches
66 conflicts
0x8cf3d245…1d0d
0x1d1325…2305
24 touches
66 conflicts
0xea7ebe9d…709e
0x1d1325…2305
24 touches
66 conflicts
0xdb067026…9eb8
0x1d1325…2305
24 touches
66 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
78 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity